[Bug target/77586] [7 Regression] ia64 target fails to build due to ICE triggered by -fself-test

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77586 Richard Biener changed: What|Removed |Added Target||ia64-*-* Target Milestone|---

[Bug libgcc/71744] Concurrently throwing exceptions is not scalable

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71744 --- Comment #19 from Gleb Natapov --- (In reply to Jakub Jelinek from comment #18) > (In reply to Gleb Natapov from comment #16) > > Can you suggest an alternative to libgcc patch? Use other TLS model? > > Allocate per thread storage dynamically

[Bug c/77587] New: C compiler produces incorrect stack alignment with __attribute((weak))

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77587 Bug ID: 77587 Summary: C compiler produces incorrect stack alignment with __attribute((weak)) Product: gcc Version: 5.4.0 Status: UNCONFIRMED Severity: normal

[Bug tree-optimization/77580] Improve devirtualization

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77580 --- Comment #3 from Andrew Pinski --- I think this shows up in h264 code in spec2006.

[Bug target/77587] C compiler produces incorrect stack alignment with __attribute__((weak))

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77587 Markus Trippelsdorf changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

[Bug libgcc/71744] Concurrently throwing exceptions is not scalable

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71744 --- Comment #26 from Jakub Jelinek --- (In reply to Gleb Natapov from comment #25) > Using Torvald's rwlock would be definitely better that current state, but > not as good as per thread lock. In theory there could be e.g. an option to keep

[Bug target/77587] [5/6/7 Regression] C compiler produces incorrect stack alignment with __attribute__((weak))

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77587 Markus Trippelsdorf changed: What|Removed |Added CC||hubicka at gcc dot gnu.org ---

[Bug libgcc/71744] Concurrently throwing exceptions is not scalable

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71744 --- Comment #20 from Jakub Jelinek --- (In reply to Gleb Natapov from comment #19) > (In reply to Jakub Jelinek from comment #18) > > (In reply to Gleb Natapov from comment #16) > > > Can you suggest an alternative to libgcc patch? Use other TLS

[Bug libgcc/71744] Concurrently throwing exceptions is not scalable

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71744 --- Comment #22 from Gleb Natapov --- (In reply to torvald from comment #21) > (In reply to Jakub Jelinek from comment #17) > > (In reply to torvald from comment #15) > > > > Similarly, the 64 recursive locks in libc, again, significant amount

[Bug libgcc/71744] Concurrently throwing exceptions is not scalable

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71744 --- Comment #24 from Jakub Jelinek --- (In reply to Gleb Natapov from comment #23) > I am not sure I agree. 64 lock will take one page of memory, which is > negligible amount nowadays and we can drop the array if compiled for single > threaded

[Bug libgcc/71744] Concurrently throwing exceptions is not scalable

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71744 --- Comment #27 from Gleb Natapov --- (In reply to Jakub Jelinek from comment #26) > (In reply to Gleb Natapov from comment #25) > > Using Torvald's rwlock would be definitely better that current state, but > > not as good as per thread lock. >

[Bug debug/77589] [56/7 Regression] fortran: Missing DW_AT_byte_stride for an array record array selection

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77589 Richard Biener changed: What|Removed |Added Target||x86_64-*-* Target Milestone|---

[Bug libgcc/71744] Concurrently throwing exceptions is not scalable

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71744 --- Comment #23 from Gleb Natapov --- (In reply to Jakub Jelinek from comment #20) > (In reply to Gleb Natapov from comment #19) > > (In reply to Jakub Jelinek from comment #18) > > > (In reply to Gleb Natapov from comment #16) > > > > Can you

[Bug target/71767] Endless stream of warnings when using GCC with -Wa,-q and Clang Integrated Assembler

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71767 --- Comment #5 from Jeffrey Walton --- (In reply to Dominique d'Humieres from comment #4) > I see the problem after having updated to Xcode 8.0. I am currently testing > the following patch > Just an FYI... Clang 3.7 and below do not witness

[Bug sanitizer/69539] ICE in expand_UBSAN_NULL, at internal-fn.c:202

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69539 --- Comment #5 from Martin Liška --- I can also confirm the ICE on 4.9.0+, as well as on all active branches.

[Bug target/77587] [5/6/7 Regression] C compiler produces incorrect stack alignment with __attribute__((weak))

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77587 Richard Biener changed: What|Removed |Added Keywords||wrong-code Target Milestone|---

[Bug libgcc/71744] Concurrently throwing exceptions is not scalable

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71744 --- Comment #21 from torvald at gcc dot gnu.org --- (In reply to Jakub Jelinek from comment #17) > (In reply to torvald from comment #15) > > > Similarly, the 64 recursive locks in libc, again, significant amount of > > > memory > > > per process

[Bug libgcc/71744] Concurrently throwing exceptions is not scalable

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71744 --- Comment #25 from Gleb Natapov --- (In reply to Jakub Jelinek from comment #24) > (In reply to Gleb Natapov from comment #23) > > I am not sure I agree. 64 lock will take one page of memory, which is > > negligible amount nowadays and we can

[Bug debug/77589] New: fortran: Missing DW_AT_byte_stride for an array record array selection

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77589 Bug ID: 77589 Summary: fortran: Missing DW_AT_byte_stride for an array record array selection Product: gcc Version: 6.2.1 Status: UNCONFIRMED Severity: normal

[Bug target/71767] Endless stream of warnings when using GCC with -Wa,-q and Clang Integrated Assembler

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71767 Dominique d'Humieres changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

[Bug target/71767] Endless stream of warnings when using GCC with -Wa,-q and Clang Integrated Assembler

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71767 --- Comment #6 from Dominique d'Humieres --- > Just an FYI... Clang 3.7 and below do not witness the problem. > Clang 3.8 and above do. > ... Thanks for the tip, but I don't use MacPorts. I am building and testing gcc myself with the Apple's

[Bug debug/77589] fortran: Missing DW_AT_byte_stride for an array record array selection

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77589 --- Comment #1 from Jan Kratochvil --- Created attachment 39617 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=39617=edit dwarf-stridex.f90

[Bug tree-optimization/77580] Improve devirtualization

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77580 --- Comment #2 from Richard Biener --- Note that for inlining to kick in this all has to be done during early optimization which is somewhat against its intent (perform transforms reducing code-size). Putting x > 10 ? f1 : f2 into the loop is

[Bug sanitizer/69539] ICE in expand_UBSAN_NULL, at internal-fn.c:202

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69539 --- Comment #6 from Martin Liška --- There's a minimal test-case: int fn1 (void) { return *(volatile int *) fn1; }

[Bug c++/77588] New: Internal error triggered by __builtin___chkp_bndret

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77588 Bug ID: 77588 Summary: Internal error triggered by __builtin___chkp_bndret Product: gcc Version: 5.4.0 Status: UNCONFIRMED Severity: normal Priority: P3

[Bug sanitizer/69539] ICE in expand_UBSAN_NULL, at internal-fn.c:202

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69539 --- Comment #4 from Marek Polacek --- That's weird, I can still reproduce: $ xgcc -flto -fsanitize=null -c -o test test.c $ xgcc -flto test include/linux/compiler.h: In function ‘__read_once_size_nocheck’: include/linux/compiler.h:235:44:

[Bug c++/77591] New: decltype(auto) and ternary operator allow returning local reference without a warning

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77591 Bug ID: 77591 Summary: decltype(auto) and ternary operator allow returning local reference without a warning Product: gcc Version: 6.2.0 Status: UNCONFIRMED

[Bug c++/77592] New: GCC: Compile failures with delegated constructor circular reference

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77592 Bug ID: 77592 Summary: GCC: Compile failures with delegated constructor circular reference Product: gcc Version: 5.3.1 Status: UNCONFIRMED Severity: normal

[Bug c++/77592] gcc accepts delegated constructor with circular reference

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77592 Markus Trippelsdorf changed: What|Removed |Added Keywords||accepts-invalid

[Bug libstdc++/77582] Improve std::string::clear performace

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77582 Jonathan Wakely changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

[Bug fortran/77584] Unclassifiable statement error with procedure pointer using template named "structure_"

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77584 --- Comment #1 from Fritz Reese --- Created attachment 39618 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=39618=edit Patch for PR 77584 The attached patch fixes the issue. 2016-09-14 Fritz Reese

[Bug c++/77591] [6/7 Regression] decltype(auto) and ternary operator allow returning local reference without a warning

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77591 --- Comment #2 from Marc Glisse --- Before delayed folding, the conditional was probably eliminated before we even reached the warning code in the front-end. The warning is duplicated in the middle-end precisely because in some cases we need

[Bug fortran/77583] ICE in pp_quoted_string, at pretty-print.c:966

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77583 --- Comment #3 from Dominique d'Humieres --- > check_conflict is sometimes called with name = NULL and that is passed > to %qs causing a crash. Indeed, but this is not the case for the tests giving the error Error: internal procedure '*' at

[Bug c++/77592] gcc accepts delegated constructor with circular reference

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77592 --- Comment #2 from Jonathan Wakely --- (In reply to Gawain Bolton from comment #0) > Compilation segfaults using gcc v5.3, v6.1 and gcc HEAD 7.0.0 20160913 Compilation works fine, the executable segfaults, due to a stack overflow. The

[Bug fortran/74600] [openacc] duplicate data map error

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=74600 Thomas Schwinge changed: What|Removed |Added CC||jakub at gcc dot gnu.org --- Comment

[Bug c++/77539] gcc-5/6: comparison of array to nullptr failure in constexpr (fixed by r235506 on trunk)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77539 --- Comment #1 from Nathan Sidwell --- Author: nathan Date: Wed Sep 14 14:29:01 2016 New Revision: 240136 URL: https://gcc.gnu.org/viewcvs?rev=240136=gcc=rev Log: cp/ PR c++/77539 * constexpr.c (get_fundef_copy): Use the

[Bug c++/77591] [6/7 Regression] decltype(auto) and ternary operator allow returning local reference without a warning

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77591 Jonathan Wakely changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

[Bug c/77590] va_arg() returns 0

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77590 --- Comment #1 from negge at dgql dot org --- Created attachment 39620 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=39620=edit com.ld

[Bug c/77590] New: va_arg() returns 0

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77590 Bug ID: 77590 Summary: va_arg() returns 0 Product: gcc Version: 6.1.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee:

[Bug c++/77539] gcc-5/6: comparison of array to nullptr failure in constexpr (fixed by r235506 on trunk)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77539 Nathan Sidwell changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug c++/77592] gcc accepts delegated constructor with circular reference

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77592 --- Comment #3 from Gawain Bolton --- You are absolutely right, it is my program that seg faults and not GCC. As you suggest, it would be great if GCC could give a diagnostic for delegated constructor circular references.

[Bug rtl-optimization/77289] [7 Regression] ICE in extract_constrain_insn, at recog.c:2212 on powerpc64

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77289 Bill Schmidt changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug c++/77539] gcc-5/6: comparison of array to nullptr failure in constexpr (fixed by r235506 on trunk)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77539 --- Comment #2 from Nathan Sidwell --- Author: nathan Date: Wed Sep 14 16:13:52 2016 New Revision: 240138 URL: https://gcc.gnu.org/viewcvs?rev=240138=gcc=rev Log: PR c++/77539 * g++.dg/cpp1y/pr77539.C: New. Added:

[Bug fortran/77593] New: configure-target-libgfortran " cygwin64 Windows 10 anniversary

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77593 Bug ID: 77593 Summary: configure-target-libgfortran " cygwin64 Windows 10 anniversary Product: gcc Version: 7.0 Status: UNCONFIRMED Severity: normal

[Bug target/77586] [7 Regression] ia64 target fails to build due to ICE triggered by -fself-test

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77586 --- Comment #1 from joseph at codesourcery dot com --- My offer at to provide an untested patch to always enable TFmode support in libgcc on ia64, if such an untested patch would be

[Bug libgcc/71744] Concurrently throwing exceptions is not scalable

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71744 --- Comment #28 from torvald at gcc dot gnu.org --- (In reply to Jakub Jelinek from comment #20) > (In reply to Gleb Natapov from comment #19) > > (In reply to Jakub Jelinek from comment #18) > > > (In reply to Gleb Natapov from comment #16) > >

[Bug target/71767] Endless stream of warnings when using GCC with -Wa,-q and Clang Integrated Assembler

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71767 --- Comment #8 from Jeffrey Walton --- (In reply to Iain Sandoe from comment #7) > (In reply to Dominique d'Humieres from comment #4) > > I see the problem after having updated to Xcode 8.0. I am currently testing > > the following patch > > >

[Bug target/71767] Endless stream of warnings when using GCC with -Wa,-q and Clang Integrated Assembler

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71767 --- Comment #7 from Iain Sandoe --- (In reply to Dominique d'Humieres from comment #4) > I see the problem after having updated to Xcode 8.0. I am currently testing > the following patch > /* The .text section is generated in varasm.c */ >

[Bug target/71767] Endless stream of warnings when using GCC with -Wa,-q and Clang Integrated Assembler

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71767 --- Comment #9 from Iain Sandoe --- (In reply to Jeffrey Walton from comment #8) > (In reply to Iain Sandoe from comment #7) > > (In reply to Dominique d'Humieres from comment #4) > > > I see the problem after having updated to Xcode 8.0. I am

[Bug bootstrap/77593] [7 Regression] Bootstrap failure with configure-target-libgfortran " cygwin64 Windows 10 anniversary

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77593 --- Comment #2 from tprince at computer dot org --- I suspect the Windows 10 provided svn may be partly at fault (although it works for bootstrapping on the Microsoft provided gcc in linux subsystem). I grabbed trunk using cygwin svn and have

[Bug c++/77549] [7 Regression] ICE on invalid C++ code that references undeclared variable

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77549 --- Comment #3 from Jakub Jelinek --- Author: jakub Date: Wed Sep 14 21:55:10 2016 New Revision: 240148 URL: https://gcc.gnu.org/viewcvs?rev=240148=gcc=rev Log: PR c++/77549 * name-lookup.c (consider_binding_level): Look through

[Bug bootstrap/77593] [7 Regression] Bootstrap failure with configure-target-libgfortran " cygwin64 Windows 10 anniversary

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77593 Thomas Koenig changed: What|Removed |Added Target||x86_64-unknown-cygwin

[Bug target/71767] Endless stream of warnings when using GCC with -Wa,-q and Clang Integrated Assembler

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71767 --- Comment #10 from Jeffrey Walton --- > than adjusting section definitions - we need to change which ones are >> > selected in config/darwin.c >> > >> I _think_ you can detect which linker at runtime with something like the >> following: >>

[Bug middle-end/77594] New: double computation for __builtin_sub_overflow (0, ...)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77594 Bug ID: 77594 Summary: double computation for __builtin_sub_overflow (0, ...) Product: gcc Version: 6.2.1 Status: UNCONFIRMED Severity: normal Priority: P3

[Bug libgcc/71744] Concurrently throwing exceptions is not scalable

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71744 --- Comment #15 from torvald at gcc dot gnu.org --- (In reply to Jakub Jelinek from comment #14) > Looking at that patchset, I just want to say that the use of TLS in libgcc > is very much undesirable, it affects every program even when not using

[Bug libgcc/71744] Concurrently throwing exceptions is not scalable

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71744 --- Comment #16 from Gleb Natapov --- Can you suggest an alternative to libgcc patch? Use other TLS model? Allocate per thread storage dynamically somehow? About lock array, I tries to use rwlock and the current one is not better than regular

[Bug libgcc/71744] Concurrently throwing exceptions is not scalable

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71744 --- Comment #17 from Jakub Jelinek --- (In reply to torvald from comment #15) > > Similarly, the 64 recursive locks in libc, again, significant amount of > > memory > > per process that doesn't care about exceptions, > > That might be reducable

[Bug libgcc/71744] Concurrently throwing exceptions is not scalable

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71744 --- Comment #18 from Jakub Jelinek --- (In reply to Gleb Natapov from comment #16) > Can you suggest an alternative to libgcc patch? Use other TLS model? > Allocate per thread storage dynamically somehow? If we want to use TLS (which I hope we

[Bug target/77590] va_arg() returns 0

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77590 Andrew Pinski changed: What|Removed |Added Component|c |target --- Comment #2 from Andrew

[Bug fortran/77583] ICE in pp_quoted_string, at pretty-print.c:966

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77583 kargl at gcc dot gnu.org changed: What|Removed |Added CC||kargl at gcc dot gnu.org ---

[Bug target/71767] Endless stream of warnings when using GCC with -Wa,-q and Clang Integrated Assembler

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71767 --- Comment #11 from Jeremy Huddleston Sequoia --- (In reply to Jeffrey Walton from comment #5) ># port install clang-3.8 ># port install gcc6 ># ln -s /opt/local/bin/clang /opt/local/bin/clang-3.8 You probably meant: $ ln -s

[Bug middle-end/77574] Wrong if condition in predict.c

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77574 --- Comment #3 from Martin Liška --- Author: marxin Date: Wed Sep 14 07:18:53 2016 New Revision: 240128 URL: https://gcc.gnu.org/viewcvs?rev=240128=gcc=rev Log: Add braces to a condition in predict.c (PR middle-end/77574) Martin

[Bug middle-end/77574] Wrong if condition in predict.c

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77574 Martin Liška changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug target/77586] New: ia64 target fails to build due to ICE triggered by -fself-test

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77586 Bug ID: 77586 Summary: ia64 target fails to build due to ICE triggered by -fself-test Product: gcc Version: 7.0 Status: UNCONFIRMED Severity: normal

[Bug sanitizer/69539] ICE in expand_UBSAN_NULL, at internal-fn.c:202

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69539 --- Comment #3 from Jakub Jelinek --- I can't reproduce this, either with 6.x nor trunk, with -O0 I'm getting various error: call to ‘__compiletime_assert_149’ declared with attribute error: BUILD_BUG_ON failed: MODULES_VADDR <

[Bug libgcc/71744] Concurrently throwing exceptions is not scalable

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71744 --- Comment #14 from Jakub Jelinek --- Looking at that patchset, I just want to say that the use of TLS in libgcc is very much undesirable, it affects every program even when not using exceptions (significant portion of them), especially when it

[Bug libgcc/71744] Concurrently throwing exceptions is not scalable

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71744 --- Comment #11 from Gleb Natapov --- Jakub, can you apply your path please? As you've said glibc will also have to be fixed and I am working on it, but without that patch fixing glibc will not help either.

[Bug tree-optimization/77536] Vectorizer not maintaining relationship of relative block frequencies in absence of real profile data

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77536 Richard Biener changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

[Bug libgcc/71744] Concurrently throwing exceptions is not scalable

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71744 --- Comment #12 from Jakub Jelinek --- I'll bootstrap/regtest it today. That said, have you done any scalability benchmarking with/without that patch?

[Bug libgcc/71744] Concurrently throwing exceptions is not scalable

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71744 --- Comment #13 from Gleb Natapov --- I've done it with my version of it which does basically the same. The patch by itself has no effect on scalability, but in conjunction with this fix for glibc https://patchwork.ozlabs.org/patch/652301/ I get

[Bug sanitizer/68260] false positive with tsan

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68260 --- Comment #9 from Jakub Jelinek --- Author: jakub Date: Wed Sep 14 09:01:49 2016 New Revision: 240129 URL: https://gcc.gnu.org/viewcvs?rev=240129=gcc=rev Log: PR sanitizer/68260 * tsan.c: Include target.h. (enum

[Bug target/71767] Endless stream of warnings when using GCC with -Wa,-q and Clang Integrated Assembler

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71767 --- Comment #12 from Jeremy Huddleston Sequoia --- (In reply to Iain Sandoe from comment #9) > we ought not be in a position where we detect that the ld64 is too old at > the same time as trying to use the LLVM back end as the assembler. It is

[Bug preprocessor/12258] -Wold-style-cast triggers on casts in macros from system headers

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=12258 olly at survex dot com changed: What|Removed |Added CC||olly at survex dot com ---