public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "steven at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/20497] Building Code on AMD 64bits c
Date: Thu, 17 Mar 2005 00:04:00 -0000	[thread overview]
Message-ID: <20050317000404.30870.qmail@sourceware.org> (raw)
In-Reply-To: <20050316170723.20497.ajve@chevrontexaco.com>


------- Additional Comments From steven at gcc dot gnu dot org  2005-03-17 00:04 -------
I can successfully compile your test case with the gcc that is shipped 
with SUSE 9.2 ("gcc (GCC) 3.3.4 (pre 3.3.5 20040809)"). 
 
You say you are using GCC 3.3.2, but if you have any influence on it I 
suggest you try to upgrade to the more recent GCC 3.4, or to a GCC 3.3 
based on the hammer-branch of GCC's CVS repository.  The FSF "base" 
GCC 3.3 does not support AMD64 ("hammer") very well.  The hammer-branch 
is where most of the tuning and optimizing for AMD64 was done, and the 
hammer-branch is also the code base that we at SUSE build our system 
compiler from. 
 
 

-- 


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


  parent reply	other threads:[~2005-03-17  0:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-16 17:07 [Bug c++/20497] New: " ajve at chevrontexaco dot com
2005-03-16 17:11 ` [Bug target/20497] " pinskia at gcc dot gnu dot org
2005-03-16 17:16 ` pinskia at gcc dot gnu dot org
2005-03-17  0:04 ` steven at gcc dot gnu dot org [this message]
2005-03-17  0:06 ` steven at gcc dot gnu dot org
2005-03-17  0:10 ` ajve at chevrontexaco dot com
2005-03-17  0:11 ` ajve at chevrontexaco dot com
2005-03-17 21:34 ` ajve at chevrontexaco dot com
2005-03-23  5:37 ` pinskia at gcc dot gnu dot org
2005-06-22  0:19 ` pinskia at gcc dot gnu dot org
2005-06-25 11:41 ` steven 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=20050317000404.30870.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).