This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/82005] [8 regression] early lto debug creates invalid assembly on Darwin
- From: "rguenther at suse dot de" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 30 Aug 2017 19:26:01 +0000
- Subject: [Bug target/82005] [8 regression] early lto debug creates invalid assembly on Darwin
- Auto-submitted: auto-generated
- References: <bug-82005-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82005
--- Comment #11 from rguenther at suse dot de <rguenther at suse dot de> ---
On August 30, 2017 8:18:07 PM GMT+02:00, "dominiq at lps dot ens.fr"
<gcc-bugzilla@gcc.gnu.org> wrote:
>https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82005
>
>--- Comment #10 from Dominique d'Humieres <dominiq at lps dot ens.fr>
>---
>I can prune the warnings with
>
> regsub -all "(^|\n)while processing\[^\n\]*" $text "" text
>regsub -all "(^|\n)warning: could not find referenced DIE" $text ""
>text
>
>however I see failures of the kind
>
>collect2: fatal error: dsymutil terminated with signal 11 [Segmentation
>fault:
>11]
>compilation terminated.
On LTO tescases or on others? LTO is expected to fail in weird ways until
simple object support for mach-o is implemented.