https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69408
Andrew Pinski changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69408
--- Comment #15 from night_ghost at ykoctpa dot ru ---
steps to repeat:
Arduino recent version should be installed
GCC created by the above script should be in PATH and in Arduino's
/usr/share/arduino/hardware/tools/avr
un-tar testcase, cd to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69408
--- Comment #14 from night_ghost at ykoctpa dot ru ---
Created attachment 37487
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=37487&action=edit
script to build GCC-avr and other tools
use this script to build GCC
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69408
--- Comment #13 from Uroš Bizjak ---
(In reply to Uroš Bizjak from comment #12)
> Created attachment 37478 [details]
> libgcov.a
>
> At the end of the day, it looks like a ld.bfd bug.
I have taken this specific x86_64 problem to Red Hat Bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69408
--- Comment #12 from Uroš Bizjak ---
Created attachment 37478
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=37478&action=edit
libgcov.a
At the end of the day, it looks like a ld.bfd bug.
Starting program: /usr/bin/ld.bfd --eh-frame-hdr -
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69408
--- Comment #11 from Uroš Bizjak ---
Created attachment 37477
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=37477&action=edit
object file of the failing test
Maybe attached object file will help:
$ /ssd/uros/gcc-build/prev-gcc/collect2 -
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69408
--- Comment #10 from Uroš Bizjak ---
(In reply to Martin Liška from comment #9)
> I'm not so lucky to reproduce the segfault. Are you running a current trunk
> revision? What version of ld do you have?
I have the latest (and fully updated) Fedo
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69408
--- Comment #9 from Martin Liška ---
(In reply to Uroš Bizjak from comment #8)
> The ld segfault can also be triggered outside testsuite with:
>
> /ssd/uros/gcc-build/gcc/xgcc -B /ssd/uros/gcc-build/gcc -O2 -fprofile-arcs
> -flto -r -nostdlib -f
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69408
--- Comment #8 from Uroš Bizjak ---
The ld segfault can also be triggered outside testsuite with:
/ssd/uros/gcc-build/gcc/xgcc -B /ssd/uros/gcc-build/gcc -O2 -fprofile-arcs
-flto -r -nostdlib -fno-use-linker-plugin 20100430-1_0.c
collect2: fata
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69408
--- Comment #7 from Uroš Bizjak ---
Yes.
Using RUNTESTFLAGS="--target_board=unix/-fno-use-linker-plugin" on
x86_64-linux-gnu, I got:
UNRESOLVED: gcc.dg/lto/20100430-1 c_lto_20100430-1_0.o-c_lto_20100430-1_0.o
execute -O2 -fprofile-arcs -flto -r
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69408
--- Comment #6 from Martin Liška ---
(In reply to night_ghost from comment #4)
> I can attach script which GCC has been built, and ZIP of the project tree
> which cause crash.
Hi.
That would be beneficial!
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69408
Uroš Bizjak changed:
What|Removed |Added
CC||ubizjak at gmail dot com
--- Comment #5 fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69408
--- Comment #4 from night_ghost at ykoctpa dot ru ---
I can attach script which GCC has been built, and ZIP of the project tree which
cause crash.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69408
Martin Liška changed:
What|Removed |Added
CC||marxin at gcc dot gnu.org
--- Comment #3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69408
--- Comment #2 from night_ghost at ykoctpa dot ru ---
there are reqirements for reporting *language* bugs but no LTO bugs in
https://gcc.gnu.org/bugs.html
I can ZIP build tree but I saw a list of all that i can send in the "we do not
want". Crash
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69408
Richard Biener changed:
What|Removed |Added
Target||avr
Status|UNCONFIRMED
16 matches
Mail list logo
