public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sje at cup dot hp dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/39631] New: f951 seg faults while building libgfortran Date: Fri, 03 Apr 2009 20:20:00 -0000 [thread overview] Message-ID: <bug-39631-3107@http.gcc.gnu.org/bugzilla/> (raw) f951 generates a seg fault while building on hppa1.1-hp-hpux11.11. It can be reproduced by compiling the following fortran code with -O2 optimization: elemental function gfortran_specific_dim_r16 (p1, p2) real (kind=16), intent (in) :: p1, p2 real (kind=16) :: gfortran_specific_dim_r16 gfortran_specific_dim_r16 = dim (p1, p2) end function The segfault is coming from the ira_assert in ira_reuse_stack_slot at line 2966 of ira-color.c. allocno is NULL but gets dereferenced in the ALLOCNO_HARD_REGNO macro. It started failing sometime before r145385 and after r145268. During that period the compiler was not building correctly on PA so I don't yet know exactly what change broke it. -- Summary: f951 seg faults while building libgfortran Product: gcc Version: 4.5.0 Status: UNCONFIRMED Keywords: build Severity: normal Priority: P3 Component: bootstrap AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: sje at cup dot hp dot com GCC target triplet: hppa1.1-hp-hpux11.11 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39631
next reply other threads:[~2009-04-03 20:20 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-04-03 20:20 sje at cup dot hp dot com [this message] 2009-04-03 21:19 ` [Bug bootstrap/39631] " sje at cup dot hp dot com 2009-04-03 21:32 ` hjl dot tools at gmail dot com 2009-04-03 21:37 ` vmakarov at redhat dot com 2009-04-03 21:40 ` sje at cup dot hp dot com 2009-04-03 22:26 ` hjl at gcc dot gnu dot org 2009-04-12 18:44 ` danglin at gcc dot gnu dot org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-39631-3107@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).