[Bug debug/90441] [9 regression] corrupt debug info with LTO

2019-05-12 Thread hoganmeier at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90441 --- Comment #3 from krux --- Finally tried qemu+gdb on the original code: gdb-8.2.1/gdb/dwarf2read.c:9715: internal-error: void dw2_add_symbol_to_list(symbol*, pending**): Assertion `(*listhead) == NULL || (SYMBOL_LANGUAGE

OGW提%%供%%税%%栗%rc

2019-05-12 Thread mrtdsyt
gcc-bugs@gcc.gnu.org + 快何 可 办 税 票,认 证 后 付 歀。 详 电:李 生,136—6075— 4190, 业 q:157— 533— 2698 ---

[Bug c++/90172] [8/9/10 Regression] ICE: Segmentation fault (in contains_struct_check)

2019-05-12 Thread asolokha at gmx dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90172 Arseny Solokha changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug c++/90265] [9/10 Regression] ICE in build_call_a at gcc/cp/call.c:396 since r268377

2019-05-12 Thread asolokha at gmx dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90265 Arseny Solokha changed: What|Removed |Added CC||asolokha at gmx dot com --- Comment #9

[Bug c++/90448] New: [8/9/10 Regression] decltype-based lambda parameter pack is rejected

2019-05-12 Thread asolokha at gmx dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90448 Bug ID: 90448 Summary: [8/9/10 Regression] decltype-based lambda parameter pack is rejected Product: gcc Version: 9.0 Status: UNCONFIRMED Keywords:

[Bug tree-optimization/90447] New: Missed opportunities to use adc (worse when -1 is involved)

2019-05-12 Thread cassio.neri at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90447 Bug ID: 90447 Summary: Missed opportunities to use adc (worse when -1 is involved) Product: gcc Version: 9.1.0 Status: UNCONFIRMED Severity: normal

[Bug d/90446] New: ICE: Segmentation fault in build_function_type at gcc/tree.c:8539

2019-05-12 Thread ibuclaw at gdcproject dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90446 Bug ID: 90446 Summary: ICE: Segmentation fault in build_function_type at gcc/tree.c:8539 Product: gcc Version: 9.0 Status: UNCONFIRMED Severity: normal

[Bug libstdc++/90442] std::pmr::new_delete_resource->allocate results in UBSan error member call on address ... which does not point to an object of type 'memory_resource'

2019-05-12 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90442 Jonathan Wakely changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug c++/67371] Never executed "throw" in constexpr function fails to compile

2019-05-12 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67371 --- Comment #16 from Jonathan Wakely --- I'd guess it was fixed by the patch for PR 86678.

[Bug d/90445] New: internal compiler error: in d_build_c_type_nodes, at d/d-builtins.cc:783

2019-05-12 Thread ibuclaw at gdcproject dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90445 Bug ID: 90445 Summary: internal compiler error: in d_build_c_type_nodes, at d/d-builtins.cc:783 Product: gcc Version: 9.0 Status: UNCONFIRMED Severity: normal

[Bug pch/90306] ICE when using precompiled headers with -MD and -fpch-deps

2019-05-12 Thread pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90306 Andrew Pinski changed: What|Removed |Added Known to fail||7.3.0 --- Comment #3 from Andrew Pinski

[Bug bootstrap/90418] [10 Regression] powerpc-darwin9 bootstrap fails after r271013

2019-05-12 Thread iains at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90418 --- Comment #12 from Iain Sandoe --- (In reply to David Edelsohn from comment #11) > Created attachment 46345 [details] > AIX EH sibcall patch > > This patch seems to fix the EH failures on AIX. > > Because of Darwin use of save_world, Darwin

[Bug bootstrap/90418] [10 Regression] powerpc-darwin9 bootstrap fails after r271013

2019-05-12 Thread dje at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90418 --- Comment #11 from David Edelsohn --- Created attachment 46345 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46345=edit AIX EH sibcall patch This patch seems to fix the EH failures on AIX. Because of Darwin use of save_world, Darwin

[Bug target/82920] cet test failures on darwin

2019-05-12 Thread iains at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82920 --- Comment #8 from Iain Sandoe --- Author: iains Date: Sun May 12 19:07:49 2019 New Revision: 271110 URL: https://gcc.gnu.org/viewcvs?rev=271110=gcc=rev Log: x86 - fix pr82920 The various thunks output codes have inconsisten output

[Bug d/90444] New: internal compiler error: in d_init_builtins, at d/d-builtins.cc:1121

2019-05-12 Thread ibuclaw at gdcproject dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90444 Bug ID: 90444 Summary: internal compiler error: in d_init_builtins, at d/d-builtins.cc:1121 Product: gcc Version: 9.0 Status: UNCONFIRMED Severity: normal

[Bug driver/90443] New: -flto=n on Windows results in CreateProcess: No such file or directory

2019-05-12 Thread hoganmeier at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90443 Bug ID: 90443 Summary: -flto=n on Windows results in CreateProcess: No such file or directory Product: gcc Version: 9.1.0 Status: UNCONFIRMED Severity: normal

[Bug libstdc++/90442] New: std::pmr::new_delete_resource->allocate results in UBSan error member call on address ... which does not point to an object of type 'memory_resource'

2019-05-12 Thread laurynas.biveinis at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90442 Bug ID: 90442 Summary: std::pmr::new_delete_resource->allocate results in UBSan error member call on address ... which does not point to an object of type 'memory_resource'

[Bug debug/90441] [9 regression] corrupt debug info with LTO

2019-05-12 Thread hoganmeier at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90441 --- Comment #2 from krux --- By the way, with 8.3 there is no DWARF error, but nm -l does not show any file location for _VectorsFlash either.

[Bug debug/90441] [9 regression] corrupt debug info with LTO

2019-05-12 Thread hoganmeier at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90441 --- Comment #1 from krux --- Created attachment 46343 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46343=edit llvm-dwarfdump --verify output FWIW llvm-dwarfdump --verify shows the same errors for both versions, but for gcc-9 it can't

[Bug debug/90441] New: [9 regression] corrupt debug info with LTO

2019-05-12 Thread hoganmeier at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90441 Bug ID: 90441 Summary: [9 regression] corrupt debug info with LTO Product: gcc Version: 9.0 Status: UNCONFIRMED Keywords: needs-bisection Severity: normal

[Bug c/90440] New: Solaris 10 sparcs fails to find

2019-05-12 Thread jullien at eligis dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90440 Bug ID: 90440 Summary: Solaris 10 sparcs fails to find Product: gcc Version: 8.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c

[Bug gcov-profile/90439] New: [GCOV] multiple expression across different lines in if statement is inconsistent when the body is empty

2019-05-12 Thread yangyibiao at nju dot edu.cn
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90439 Bug ID: 90439 Summary: [GCOV] multiple expression across different lines in if statement is inconsistent when the body is empty Product: gcc Version: 9.0 Status:

[Bug gcov-profile/90438] New: [GCOV] switch statement is not instrumented when "case" body is empty and only "default" body with statements

2019-05-12 Thread yangyibiao at nju dot edu.cn
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90438 Bug ID: 90438 Summary: [GCOV] switch statement is not instrumented when "case" body is empty and only "default" body with statements Product: gcc Version: 9.0

[Bug tree-optimization/90437] New: Overflow detection too late for VRP

2019-05-12 Thread glisse at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90437 Bug ID: 90437 Summary: Overflow detection too late for VRP Product: gcc Version: 10.0 Status: UNCONFIRMED Keywords: missed-optimization Severity: normal

[Bug middle-end/90435] gcc generate infinite loop code when using -O2 or -O3

2019-05-12 Thread sch...@linux-m68k.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90435 Andreas Schwab changed: What|Removed |Added Resolution|FIXED |INVALID

[Bug libstdc++/90436] Redundant size checking in vector

2019-05-12 Thread glisse at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90436 --- Comment #1 from Marc Glisse --- Adding if(size()>max_size())__builtin_unreachable()) sometimes helps, depending where you add it and in what exact form.

[Bug middle-end/90435] gcc generate infinite loop code when using -O2 or -O3

2019-05-12 Thread pangqingyuan1991 at 163 dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90435 庞庆源 changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug middle-end/90435] gcc generate infinite loop code when using -O2 or -O3

2019-05-12 Thread pangqingyuan1991 at 163 dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90435 --- Comment #4 from 庞庆源 --- (In reply to Marc Glisse from comment #3) > (In reply to 庞庆源 from comment #2) > > gcc pmalloc.c -O2 -o ppp -ldl -fno-tree-loop-distribute-patterns > > -fno-strict-aliasing > > Still not work. > > -fno-builtin (the

[Bug libstdc++/87544] alloc-size-larger-than incorrectly triggered

2019-05-12 Thread glisse at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87544 --- Comment #20 from Marc Glisse --- I created bug 90436 about the excessive checking so it does not distract from the warning that this bug is about (and doesn't get lost either).

[Bug libstdc++/90436] New: Redundant size checking in vector

2019-05-12 Thread glisse at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90436 Bug ID: 90436 Summary: Redundant size checking in vector Product: gcc Version: 10.0 Status: UNCONFIRMED Keywords: missed-optimization Severity: normal

[Bug middle-end/89230] Bogus uninited usage warning

2019-05-12 Thread egallager at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89230 --- Comment #7 from Eric Gallager --- (In reply to Andrew Pinski from comment #3) > (In reply to lavr from comment #2) > > Okay, but "d" points to a clearly separate storage on stack within a local > > frame. None of the pointers passed to