[Bug c++/108737] New: Apparent miscompile of infinite loop on gcc trunk in cddce2 pass

Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: njs at pobox dot com Target Milestone: --- There's a meme going around about strange compilation outputs caused infinite-loop-related UB, and while discussing it a friend stumbled

[Bug libgomp/60035] [PATCH] make it possible to use OMP on both sides of a fork (without violating standard)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60035 --- Comment #13 from Nathaniel J. Smith --- Unfortunately, AFAICT, the omp_pause_resource APIs don't actually solve the problem. They're fine and useful if you have a single piece of code that wants to use both omp and fork(). But, this was

[Bug target/55307] libgcc's __cpu_indicator_init does not check for avx correctly

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55307 Nathaniel J. Smith changed: What|Removed |Added CC||njs at pobox dot com --- Comment

[Bug target/85100] __builtin_cpu_supports avx does not verify OS supports it

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85100 --- Comment #5 from Nathaniel J. Smith --- Julian, are you able to test the patch? I don't have a reproduction setup currently...

[Bug target/85100] __builtin_cpu_supports avx does not verify OS supports it

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85100 --- Comment #3 from Nathaniel J. Smith --- We're using it exactly like the docs recommend. What on earth is __builtin_cpu_supports for, if not to tell you whether you can use a given feature? If this is by design, than at the very least the

[Bug target/85100] __builtin_cpu_supports avx does not verify OS supports it

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85100 Nathaniel J. Smith changed: What|Removed |Added CC||njs at pobox dot com --- Comment

[Bug libgomp/60035] [PATCH] make it possible to use OMP on both sides of a fork (without violating standard)

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60035 Nathaniel J. Smith njs at pobox dot com changed: What|Removed |Added Attachment #32019|0 |1

[Bug libgomp/60035] [PATCH] make it possible to use OMP on both sides of a fork (without violating standard)

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60035 --- Comment #6 from Nathaniel J. Smith njs at pobox dot com --- (In reply to larsmans from comment #4) Nathaniel, could you apply the cosmetic changes suggested at http://gcc.gnu.org/ml/gcc-patches/2014-02/msg00860.html? I'd hate to see

[Bug libgomp/60035] [PATCH] make it possible to use OMP on both sides of a fork (without violating standard)

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60035 --- Comment #8 from Nathaniel J. Smith njs at pobox dot com --- (In reply to larsmans from comment #7) Phase 1? (Not familiar with the GCC dev cycle.) Sorry, meant stage 1. GCC trunk is (IIUC) currently in RC-bug-fixes-only pre-release freeze

[Bug libgomp/60035] [PATCH] make it possible to use OMP on both sides of a fork (without violating standard)

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60035 --- Comment #2 from Nathaniel J. Smith njs at pobox dot com --- Good point -- sent. http://gcc.gnu.org/ml/gcc-patches/2014-02/msg00813.html

[Bug libgomp/60035] New: [PATCH] make it possible to use OMP on both sides of a fork (without violating standard)

Severity: enhancement Priority: P3 Component: libgomp Assignee: unassigned at gcc dot gnu.org Reporter: njs at pobox dot com CC: jakub at gcc dot gnu.org Created attachment 32019 -- http://gcc.gnu.org/bugzilla/attachment.cgi?id=32019action