public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/56564] movdqa on possibly-8-byte-aligned struct with -O3
Date: Tue, 11 Jun 2013 15:11:00 -0000	[thread overview]
Message-ID: <bug-56564-4-u3G54RKSwP@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56564-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56564

--- Comment #18 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
(In reply to comment #17)
> Yeah, MachO is broken by design, guess the tests need to be restricted 
> to non-darwin non-PE.

Questions:
(1) What is PE?
(2) Is the second "return 0;" wrong code or valid optimization? If the former,
why?
(3) Is the decoration "__emutls_v." the same for all the emutls platforms? If
not, where can I find the variants?


  parent reply	other threads:[~2013-06-11 15:11 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-07 16:24 [Bug c++/56564] New: [4.7 Regression] " lukeocamden at gmail dot com
2013-03-07 16:27 ` [Bug c++/56564] " lukeocamden at gmail dot com
2013-03-08 10:01 ` [Bug c++/56564] " rguenth at gcc dot gnu.org
2013-03-08 10:33 ` lukeocamden at gmail dot com
2013-03-08 10:47 ` lukeocamden at gmail dot com
2013-03-08 11:09 ` lukeocamden at gmail dot com
2013-03-08 11:21 ` jakub at gcc dot gnu.org
2013-03-08 11:27 ` [Bug target/56564] " rguenth at gcc dot gnu.org
2013-03-08 11:37 ` jakub at gcc dot gnu.org
2013-03-08 12:38 ` jakub at gcc dot gnu.org
2013-04-08 15:22 ` hubicka at gcc dot gnu.org
2013-05-25 18:21 ` jakub at gcc dot gnu.org
2013-06-07 14:01 ` jakub at gcc dot gnu.org
2013-06-10 15:52 ` jakub at gcc dot gnu.org
2013-06-11  6:17 ` jakub at gcc dot gnu.org
2013-06-11  9:16 ` dominiq at lps dot ens.fr
2013-06-11  9:27 ` jakub at gcc dot gnu.org
2013-06-11 15:11 ` dominiq at lps dot ens.fr [this message]
2013-06-11 15:27 ` jakub at gcc dot gnu.org
2013-06-12  6:50 ` jakub 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-56564-4-u3G54RKSwP@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: link
Be 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).