| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
| |
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
|
|
|
|
|
|
|
| |
Hopefully gets looked into given it's needed for maturin's
tests and do not want to delay a pep517 backend too much
(not that can do maturin yet either way due to needing
cffi and virtualenv for tests too).
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Used to be done because it was straight up broken (couldn't
build), but now it's successfully causing problems and it's
not obvious for upstreams to fix these issues with mingw.
There may be real issues in dxvk & others, but support for
this is new in mingw (also only partial), and believe using
this can be considered too experimental/early "here". Still
allowing it with USE=custom-cflags for those that really want
it and don't mind if it breaks some components they don't use.
Skipping revbump given it's an unusual configuration given
users normally don't pass this in *FLAGS but rather rely
on the toolchain's defaults. mingw64-toolchain-11.0.1 will
also be keyworded in not that long for rebuilds.
Only needed for mingw runtime, so the toolchain itself is still
using it through the system-wide defaults.
May revisit eventually.
Not doing this for crossdev+mingw64-runtime main package again,
these are for more expert use in the first place.
Bug: https://bugs.gentoo.org/870136
Closes: https://bugs.gentoo.org/931512
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
|
|
|
|
| |
Signed-off-by: Michał Górny <mgorny@gentoo.org>
|
|
|
|
| |
Signed-off-by: Michał Górny <mgorny@gentoo.org>
|
|
|
|
| |
Signed-off-by: Michał Górny <mgorny@gentoo.org>
|
|
|
|
| |
Signed-off-by: Michał Górny <mgorny@gentoo.org>
|
|
|
|
| |
Signed-off-by: Michał Górny <mgorny@gentoo.org>
|
|
|
|
| |
Signed-off-by: Michał Górny <mgorny@gentoo.org>
|
|
|
|
| |
Signed-off-by: Michał Górny <mgorny@gentoo.org>
|
|
|
|
| |
Signed-off-by: Michał Górny <mgorny@gentoo.org>
|
|
|
|
| |
Signed-off-by: Michał Górny <mgorny@gentoo.org>
|
|
|
|
| |
Signed-off-by: Michał Górny <mgorny@gentoo.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I will never understand why people INSIST on "local -x GLOBAL_VAR" as
though it is somehow clean when its fundamental intention is to be
global.
End result: repeating the same block of code multiple times so you can
pseudo-globally set it locally each time you use it. *After* the code is
buggy for a while.
I have a recentish custom QA check that catches it though:
* QA Notice: cargo built package contains possibly vendored code
*
* crate tikv-jemalloc-sys: jemalloc.sym.o arena.sym.o background_thread.sym.o base.sym.o bin.sym.o bin_info.sym.o bitmap.sym.o buf_writer.sym.o cache_bin.sym.o ckh.sym.o counter.sym.o ctl.sym.o decay.sym.o ecache.sym.o div.sym.o edata.sym.o edata_cache.sym.o ehooks.sym.o emap.sym.o eset.sym.o exp_grow.sym.o extent.sym.o extent_dss.sym.o extent_mmap.sym.o fxp.sym.o san.sym.o san_bump.sym.o hook.sym.o hpa.sym.o hpa_hooks.sym.o hpdata.sym.o inspect.sym.o large.sym.o log.sym.o malloc_io.sym.o mutex.sym.o nstime.sym.o pa.sym.o pa_extra.sym.o pai.sym.o pac.sym.o pages.sym.o peak_event.sym.o prof.sym.o prof_data.sym.o prof_log.sym.o prof_recent.sym.o prof_stats.sym.o prof_sys.sym.o psset.sym.o rtree.sym.o safety_check.sym.o sc.sym.o sec.sym.o stats.sym.o sz.sym.o tcache.sym.o test_hooks.sym.o thread_event.sym.o ticker.sym.o tsd.sym.o witness.sym.o jemalloc.o arena.o background_thread.o base.o bin.o bin_info.o bitmap.o buf_writer.o cache_bin.o ckh.o counter.o ctl.o decay.o div.o ecache.o edata.o edata_cache.o ehooks.o emap.o eset.o exp_grow.o extent.o extent_dss.o extent_mmap.o fxp.o san.o san_bump.o hook.o hpa.o hpa_hooks.o hpdata.o inspect.o large.o log.o malloc_io.o mutex.o nstime.o pa.o pa_extra.o pai.o pac.o pages.o peak_event.o prof.o prof_data.o prof_log.o prof_recent.o prof_stats.o prof_sys.o psset.o rtree.o safety_check.o sc.o sec.o stats.o sz.o tcache.o test_hooks.o thread_event.o ticker.o tsd.o witness.o jemalloc.pic.o arena.pic.o background_thread.pic.o base.pic.o bin.pic.o bin_info.pic.o bitmap.pic.o buf_writer.pic.o cache_bin.pic.o ckh.pic.o counter.pic.o ctl.pic.o decay.pic.o div.pic.o ecache.pic.o edata.pic.o edata_cache.pic.o ehooks.pic.o emap.pic.o eset.pic.o exp_grow.pic.o extent.pic.o extent_dss.pic.o extent_mmap.pic.o fxp.pic.o san.pic.o san_bump.pic.o hook.pic.o hpa.pic.o hpa_hooks.pic.o hpdata.pic.o inspect.pic.o large.pic.o log.pic.o malloc_io.pic.o mutex.pic.o nstime.pic.o pa.pic.o pa_extra.pic.o pai.pic.o pac.pic.o pages.pic.o peak_event.pic.o prof.pic.o prof_data.pic.o prof_log.pic.o prof_recent.pic.o prof_stats.pic.o prof_sys.pic.o psset.pic.o rtree.pic.o safety_check.pic.o sc.pic.o sec.pic.o stats.pic.o sz.pic.o tcache.pic.o test_hooks.pic.o thread_event.pic.o ticker.pic.o tsd.pic.o witness.pic.o
* QA Notice: cargo built package contains possibly vendored code from unsolvable crates
*
* ring
Only reproducible when building with FEATURES=test, however, which I
don't usually do on syncing @world.
Signed-off-by: Eli Schwartz <eschwartz93@gmail.com>
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
|
| |
Signed-off-by: Eli Schwartz <eschwartz93@gmail.com>
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
|
| |
Closes: https://bugs.gentoo.org/879761
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
| |
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
|
| |
Bug: https://bugs.gentoo.org/573760
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
| |
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
| |
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
|
| |
Closes: https://bugs.gentoo.org/874966
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
|
| |
Closes: https://bugs.gentoo.org/929399
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
|
| |
Closes: https://bugs.gentoo.org/929835
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
| |
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
|
| |
Closes: https://bugs.gentoo.org/924429
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
| |
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
|
| |
Closes: https://bugs.gentoo.org/931647
Signed-off-by: Matt Turner <mattst88@gentoo.org>
|
|
|
|
|
| |
Closes: https://bugs.gentoo.org/898234
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
|
|
|
|
| |
Closes: https://bugs.gentoo.org/725286
Closes: https://bugs.gentoo.org/725290
Closes: https://bugs.gentoo.org/731748
Closes: https://bugs.gentoo.org/879749
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
| |
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
|
|
|
|
| |
Experimental option upstream which seems undertested and underdocumented.
Fails to build with stricter C compilers too (bug #919685).
Bug: https://bugs.gentoo.org/919685
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
|
|
|
| |
It checks after with a macro, so it's fine.
Closes: https://bugs.gentoo.org/907877
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
|
| |
Closes: https://bugs.gentoo.org/928108
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
| |
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
| |
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
|
|
|
|
| |
Includes a fix for the `fexecve` configure check.
Closes: https://bugs.gentoo.org/894614
Closes: https://bugs.gentoo.org/908829
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
|
|
|
|
|
|
| |
Closes: https://bugs.gentoo.org/931513
Closes: https://bugs.gentoo.org/931239
Closes: https://bugs.gentoo.org/931122
Signed-off-by: Christopher Byrne <salah.coronya@gmail.com>
Closes: https://github.com/gentoo/gentoo/pull/36619
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
| |
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
| |
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
|
|
|
| |
final dependency blocker is ported \o/
Signed-off-by: Eli Schwartz <eschwartz93@gmail.com>
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
| |
Signed-off-by: Patrick McLean <chutzpah@gentoo.org>
|
|
|
|
| |
Signed-off-by: Matt Jolly <kangie@gentoo.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add Ionen's clang-18 -mevex512 workaround to chromium:
clang-18 added -mevex512 (missing from 17), and then -march=native
is a bit quirky in that unlike -march=exact it goes out of its way
to disable it resulting in e.g.
-march=skylake -mavx512f = -mevex512 is auto-enabled
-march=skylake -mevex512 = not "enabled" but can be used
-march=native(skylake) -mavx512f = forced off(!)
And then units that use avx512 / pass -mavx512f (for use with runtime
cpu detection) end in build failure without evex512.
Always passing -mevex512 on a machine without avx512 "seems" safe,
it does not even set __EVEX512__ and believe won't use any avx512
instructions on a whim (__EVEX512__ does get set if add -mavx512f)
Bug: https://bugs.gentoo.org/931623
Signed-off-by: Matt Jolly <kangie@gentoo.org>
|
|
|
|
| |
Signed-off-by: Matt Jolly <kangie@gentoo.org>
|
|
|
|
| |
Signed-off-by: Matt Jolly <kangie@gentoo.org>
|
|
|
|
| |
Signed-off-by: Matt Jolly <kangie@gentoo.org>
|
|
|
|
| |
Signed-off-by: Matt Jolly <kangie@gentoo.org>
|
|
|
|
| |
Signed-off-by: Matt Jolly <kangie@gentoo.org>
|
|
|
|
| |
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
|
|
| |
Signed-off-by: Christopher Byrne <salah.coronya@gmail.com>
Closes: https://github.com/gentoo/gentoo/pull/36407
Signed-off-by: Sam James <sam@gentoo.org>
|