public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "amodra at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/65810] powerpc64 alignment of r2 insufficient for loading long-double constants Date: Mon, 20 Apr 2015 13:14:00 -0000 [thread overview] Message-ID: <bug-65810-4-7izgYF1NwG@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-65810-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65810 --- Comment #6 from Alan Modra <amodra at gmail dot com> --- It isn't seen most of the time because the failure happens only when r2 isn't 16-byte aligned (50% chance) and the r2 offset to a long double constant is n*64k+32k-8 (0.012% chance per long double). libgfortran stores paths for error messages in .rodata, so source path can affect placement of those long double constants. I'm just lucky.
next prev parent reply other threads:[~2015-04-20 13:14 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-04-20 0:10 [Bug target/65810] New: powerpc64 libgfortran alignment issue? amodra at gmail dot com 2015-04-20 1:43 ` [Bug target/65810] " jvdelisle at gcc dot gnu.org 2015-04-20 2:15 ` bergner at gcc dot gnu.org 2015-04-20 3:14 ` amodra at gmail dot com 2015-04-20 5:24 ` amodra at gmail dot com 2015-04-20 9:45 ` [Bug target/65810] powerpc64 alignment of r2 insufficient for loading long-double constants dominiq at lps dot ens.fr 2015-04-20 13:14 ` amodra at gmail dot com [this message] 2015-04-28 3:48 ` amodra at gcc dot gnu.org 2015-04-28 3:50 ` amodra at gmail dot com
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-65810-4-7izgYF1NwG@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).