This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug target/64231] [5 Regression] SIGSEGV building glibc on aarch64-linux-gnu from r217852


https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64231

--- Comment #13 from Tejas Belagod <belagod at gcc dot gnu.org> ---
(In reply to Sandra Loosemore from comment #12)
> I'm using a 4.7.3 based gcc as the host compiler (built from one of our own
> CodeBench release branches).
> 
> Regardless of whether the actual failure is reproducible, if you look at the
> code I pointed at in comment 7, there is clearly a bug here:  if
> force_const_mem returns NULL, GCC will crash, not just here but in several
> other places as well.

I tried with a build of cross aarch64-linux-gnu with 4.7.4 as the host compiler
and my gcc sources at HEAD and r217852 of trunk, but no luck! :-(


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]