public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "guillaume dot melquiond at ens-lyon dot fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/27055] Structures are copied byte by byte into function arguments
Date: Thu, 06 Apr 2006 13:05:00 -0000	[thread overview]
Message-ID: <20060406130543.15299.qmail@sourceware.org> (raw)
In-Reply-To: <bug-27055-7904@http.gcc.gnu.org/bugzilla/>



------- Comment #3 from guillaume dot melquiond at ens-lyon dot fr  2006-04-06 13:05 -------
> for -march=i{345}86 I get
> for -march=i686,pentium2,... I get

Thanks to your tests, I noticed that the change of behavior between GCC 3.4
versions was actually caused by the addition of --with-tune=686 in Debian
packages. In fact, even older versions of GCC 3.4 are doing byte-by-byte copies
once you change the -march target to at least i686. GCC 3.3 is fine though.


-- 


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


  parent reply	other threads:[~2006-04-06 13:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-06 11:46 [Bug c/27055] New: " guillaume dot melquiond at ens-lyon dot fr
2006-04-06 12:03 ` [Bug c/27055] " gdr at integrable-solutions dot net
2006-04-06 12:49 ` pluto at agmk dot net
2006-04-06 13:05 ` guillaume dot melquiond at ens-lyon dot fr [this message]
2006-04-13  1:52 ` [Bug target/27055] " pinskia at gcc dot gnu dot org
2006-04-16 18:16 ` guillaume dot melquiond at ens-lyon dot fr

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=20060406130543.15299.qmail@sourceware.org \
    --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).