public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/65342] [5 Regression] FAIL: gfortran.dg/intrinsic_(un)?pack_1.f90 -O1 execution test on powerpc-apple-darwin9 after r210201 Date: Tue, 10 Mar 2015 08:44:00 -0000 [thread overview] Message-ID: <bug-65342-4-Z2o1gZwgmb@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-65342-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65342 --- Comment #5 from Iain Sandoe <iains at gcc dot gnu.org> --- (In reply to Alan Modra from comment #4) > Here's another failing powerpc-darwin testcase due to movdi_low > (movdf_low_di and their store counterparts have the same problem of course). > > /* -m64 -O1 -S -fno-pic */ for Darwin, -mdynamic-no-pic ^ would be a real-life User case. > struct { > char c; > long l; > } __attribute__ ((__packed__)) x; > > long get_x (void) > { > return x.l; > } Thanks, Alan. I took a quick look over the weekend (out of the office last week). So, do you think I need to split things up so that the d-mode and ds-mode insn fragments can have different match conditions? - or is the issue that these patterns have no reload constraints (in which case I could at least investigate adding Y to the relevant cases)?
next prev parent reply other threads:[~2015-03-10 8:44 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-03-07 10:01 [Bug target/65342] New: " dominiq at lps dot ens.fr 2015-03-07 13:27 ` [Bug target/65342] " amodra at gmail dot com 2015-03-07 13:40 ` dominiq at lps dot ens.fr 2015-03-07 16:55 ` iains at gcc dot gnu.org 2015-03-09 12:16 ` rguenth at gcc dot gnu.org 2015-03-09 14:31 ` jakub at gcc dot gnu.org 2015-03-10 8:22 ` amodra at gmail dot com 2015-03-10 8:44 ` iains at gcc dot gnu.org [this message] 2015-03-10 12:44 ` amodra at gmail dot com 2015-03-10 12:59 ` iains at gcc dot gnu.org 2015-03-10 13:13 ` iains at gcc dot gnu.org 2015-03-10 13:33 ` amodra at gmail dot com 2015-03-10 13:36 ` amodra at gmail dot com 2015-03-16 9:38 ` iains at gcc dot gnu.org 2015-03-16 12:02 ` amodra at gmail dot com 2015-03-16 12:09 ` iains at gcc dot gnu.org 2015-03-25 14:32 ` dominiq at lps dot ens.fr 2015-04-09 10:13 ` iains at gcc dot gnu.org 2015-04-09 10:41 ` dominiq at lps dot ens.fr 2015-04-22 12:00 ` [Bug target/65342] [5/6 " jakub at gcc dot gnu.org 2015-07-16 9:17 ` rguenth at gcc dot gnu.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-65342-4-Z2o1gZwgmb@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).