https://sourceware.org/bugzilla/show_bug.cgi?id=18668
Jiong Wang jiwang at gcc dot gnu.org changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
https://sourceware.org/bugzilla/show_bug.cgi?id=18668
--- Comment #13 from cvs-commit at gcc dot gnu.org cvs-commit at gcc dot
gnu.org ---
The master branch has been updated by Jiong Wang jiw...@sourceware.org:
https://sourceware.org/bugzilla/show_bug.cgi?id=18668
--- Comment #11 from David Abdurachmanov david.abdurachmanov at gmail dot com
---
I tested it in the last couple of days and it worked fine. Details on GCC
bugzilla: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63304
--
You are receiving
https://sourceware.org/bugzilla/show_bug.cgi?id=18668
--- Comment #12 from David Abdurachmanov david.abdurachmanov at gmail dot com
---
For the record, the patch for -Wl,--defsym=foo=0x8000 fix is here
(already approved):
https://sourceware.org/ml/binutils/2015-07/msg00210.html
--
You are
https://sourceware.org/bugzilla/show_bug.cgi?id=18668
--- Comment #10 from Jiong Wang jiwang at gcc dot gnu.org ---
the patch fix OpenLoop builds is sent out for review.
https://sourceware.org/ml/binutils/2015-07/msg00137.html
NOTE, it address the OpenLoops issue only which is root cause of
https://sourceware.org/bugzilla/show_bug.cgi?id=18668
--- Comment #4 from David Abdurachmanov david.abdurachmanov at gmail dot com
---
I all process libraries except one in OpenLoops, that's enough to trigger the
issue.
You can get it here (4.7M):
https://sourceware.org/bugzilla/show_bug.cgi?id=18668
--- Comment #5 from Jiong Wang jiwang at gcc dot gnu.org ---
(In reply to David Abdurachmanov from comment #4)
I all process libraries except one in OpenLoops, that's enough to trigger
the issue.
You can get it here (4.7M):
https://sourceware.org/bugzilla/show_bug.cgi?id=18668
--- Comment #6 from David Abdurachmanov david.abdurachmanov at gmail dot com
---
My last test was with GCC 4.9.3, that did not ICE during OpenLoops compilation.
Thanks for looking into this!
--
You are receiving this mail because:
You are
https://sourceware.org/bugzilla/show_bug.cgi?id=18668
--- Comment #7 from Jiong Wang jiwang at gcc dot gnu.org ---
(In reply to David Abdurachmanov from comment #6)
My last test was with GCC 4.9.3, that did not ICE during OpenLoops
compilation.
Thanks for looking into this!
gcc 4.9.3 still
https://sourceware.org/bugzilla/show_bug.cgi?id=18668
--- Comment #9 from Jiong Wang jiwang at gcc dot gnu.org ---
(In reply to David Abdurachmanov from comment #8)
Could you point to GCC PR you mentioned? I just want to x-check why my
toolchain build works.
the gcc fix is
https://sourceware.org/bugzilla/show_bug.cgi?id=18668
--- Comment #8 from David Abdurachmanov david.abdurachmanov at gmail dot com
---
Could you point to GCC PR you mentioned? I just want to x-check why my
toolchain build works.
I will give your patch a spin once it lands, though OpenLoops
https://sourceware.org/bugzilla/show_bug.cgi?id=18668
David Abdurachmanov david.abdurachmanov at gmail dot com changed:
What|Removed |Added
CC|
https://sourceware.org/bugzilla/show_bug.cgi?id=18668
Jiong Wang jiwang at gcc dot gnu.org changed:
What|Removed |Added
Assignee|unassigned at sourceware dot org |jiwang
https://sourceware.org/bugzilla/show_bug.cgi?id=18668
--- Comment #1 from Jiong Wang jiwang at gcc dot gnu.org ---
thanks for reporting this, will double check the status
--
You are receiving this mail because:
You are on the CC list for the bug.
___
https://sourceware.org/bugzilla/show_bug.cgi?id=18668
David Abdurachmanov david.abdurachmanov at gmail dot com changed:
What|Removed |Added
Target|
https://sourceware.org/bugzilla/show_bug.cgi?id=18668
--- Comment #2 from Jiong Wang jiwang at gcc dot gnu.org ---
Looking at AArch64 backend in aarch64_type_of_stub there is a check:
2287 if ((r_type == AARCH64_R (CALL26) || r_type == AARCH64_R (JUMP26))
2288(branch_offset
https://sourceware.org/bugzilla/show_bug.cgi?id=18668
Jiong Wang jiwang at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |ASSIGNED
--
https://sourceware.org/bugzilla/show_bug.cgi?id=18668
--- Comment #3 from David Abdurachmanov david.abdurachmanov at gmail dot com
---
OpenLoops are suffering from another issue -- the offset between load
instruction and constant pool is above 1MB boundary. Yes, you cannot have huge
functions in
18 matches
Mail list logo