| Commit message (Collapse) | Author | Age | Lines |
| |
|
|
|
|
|
|
| |
Fix jar manifests.
This resolves #713
|
|
|
|
| |
This resolves #713
|
|\
| |
| | |
Remove unused variable
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
This resolves #717.
Note: this does not affect other applications because the platform
default is to use the "darknoise" background image for standalone
image, which effectively overrides a bg color.
|
| |
| |
| |
| | |
Tag #21
|
| |
| |
| |
| | |
Tag #21
|
| |
| |
| |
| | |
Tag #21
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Fix more -Wclass-memaccess warnings:
- Avoid using memset on a not-trivial types
- Avoid doing memset on non-POD structures
- Be more restrictive with memset on Array containers
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
|entryCount| tracks -- in fast-to-check manner -- the number of entries in the hashtable. But to actually enumerate entries, we have to loop through all of |table|, checking for entries that are actually live. A live entry is indicated by a zero |hash| in the entry. The |memset| would properly zero that; removing the memset will not.
It's not entirely clear whether a memset that overwrites a lot of stuff but is maybe simpler, is faster than compiler-generated likely-SIMD code that zeroes out *just* |hash| fields in all the entries. But I am going to guess that SIMD is good enough. For now, we should just do the simple and thing: don't distinguish POD and non-POD, and know that the compiler is going to recognize that |mem.addr()->~T()| is a no-op when T is trivial. So with POD, the loop should degenerate to just zeroing |hash| at consistent offset, and SIMD will eat that up, and it can't be *that* different from the memset in performance (if it is at all).
|
| | | |
|
| |/
| |
| |
| |
| |
| | |
nsTabSizes is non-trivial only because of the user-defined constructor. The idea desired here is certainly to zero all the members without listing them -- but the very act of doing so with a user-defined constructor, makes the idea impossible.
Arguably this is something that is permissible in the language, and that the warning should be tailored to permit. I don't think this falls afoul of any of the issues flagged in https://gcc.gnu.org/ml/gcc-patches/2017-06/msg01527.html for example. In the meantime, just explicitly zeroing the three member fields is easy and fixes the warnings.
|
|\ \
| |/
|/| |
Basilisk: Remove TelemetryStopwatch
|
|/ |
|
|\
| |
| | |
[PALEMOON] Align viewPartialSource with the UXP codebase
|
| | |
|
|/
|
|
| |
Tag #709.
|
|
|
|
| |
Tag #709
|
|
|
|
| |
Tag #709.
|
|\
| |
| | |
fix basilisk mac icons, executable name, and min os version
|
| |
| |
| | |
remove old mac firefox icns files and replace with basilisk icns files
|
| |
| |
| | |
fix exe name and min osx version
|
| |
| |
| | |
Minor style improvement
|
| |
| |
| |
| | |
(Damn you, github on-line editor!)
|
| |
| |
| | |
As a recommended document for governance of our project and community.
|
|/ |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Added HACL*Poly1305 32-bit (INRIA/Microsoft)
- Updated to final TLS 1.3 draft version (28)
- Removed TLS 1.3 prerelease draft limit check
- Removed NPN code
- Enabled dev/urandom-only RNG on Linux with NSS_SEED_ONLY_DEV_URANDOM for non-standard environments
- Fixed several bugs with TLS 1.3 negotiation
- Updated internal certificate store
- Added support for the TLS Record Size Limit Extension.
- Fixed CVE-2018-0495
- Various security fixes in the ASN.1 code.
|
| |
|
|\
| |
| | |
Simplify HeapSlot to make it trivially copyable
|
| |
| |
| |
| | |
This removes the constructors, which were never called since we allocate arrays of HeapSlot with pod_malloc. The destructor is only ever called explicitly since we free this memory with js_free so it has been renamed to destroy(). Also removed is an unused manual barrier.
|
| | |
|
|\ \
| | |
| | | |
Fix/silence some warnings with GCC 8
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
Silences compiler warning spam with GCC 8.
|
| | | |
|
| | | |
|
| |/
| |
| |
| | |
Silences a warning with GCC 8.
|
|\ \
| |/
|/| |
Shell quote environment variable values when dumping them in dump_env.py
|
|/
|
|
| |
The mozconfig output parsing code already (mostly) handles shell quoted strings, because that's what `set` outputs. By quoting environment variable values, we avoid a bunch of problems with "weird" values.
|
| |
|
|
|
|
| |
when building Pale Moon
|
| |
|
|\
| |
| | |
Pale Moon: macOS: Fix icons in editBookmarkOverlay
|
| | |
|
| | |
|