public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Nathan Dorfman <nathan@rtfm.net>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: target/2732: Interaction with Solaris assembler and SPARCV9 instructions
Date: Sun, 27 Jan 2002 16:06:00 -0000	[thread overview]
Message-ID: <20020128000600.22801.qmail@sources.redhat.com> (raw)

The following reply was made to PR target/2732; it has been noted by GNATS.

From: Nathan Dorfman <nathan@rtfm.net>
To: rodrigc@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
   nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: target/2732: Interaction with Solaris assembler and SPARCV9 instructions
Date: Thu, 10 Jan 2002 15:38:11 -0500

 Yep! -mcpu=ultrasparc has always worked great. I found it a bit odd
 that -mcpu=v9 would cause the compiler to generate the V9 instructions
 but not pass the flag to the assembler to grok them there. If this is
 the intended behavior, then there is no bug!
 
 Thanks for the followup.
 
 On Fri, Jan 04, 2002 at 05:37:36AM -0000, rodrigc@gcc.gnu.org wrote:
 Hi,
 > Synopsis: Interaction with Solaris assembler and SPARCV9 instructions
 > 
 > State-Changed-From-To: open->feedback
 > State-Changed-By: rodrigc
 > State-Changed-When: Thu Jan  3 21:37:35 2002
 > State-Changed-Why:
 >     Refer to the release notes at:
 >     http://gcc.gnu.org/install/specific.html#*-*-solaris2*
 >     
 >     You need to use GCC 3.1 and up.
 >     Using -mtune=ultrasparc is the safest.
 >     
 >     If you want to use -mcpu=v9, then you need to pass
 >     the assembler -xarch=v9a.
 >     So you need to do something like:
 >     gcc -Wa,-xarch=v9a
 >     
 >     See:
 >     http://gcc.gnu.org/ml/gcc-bugs/2001-05/msg00346.html
 >     
 >     Does this work for you?
 > 
 > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=2732
 
 -- 
 "Just because a few of us can read and     \  \  \\   Nathan Dorfman
 write and do a little math, that doesn't    \     \\   nathan@rtfm.net
 mean we deserve to take over the universe."  \  \  \\   PGP Key 0832DB12


             reply	other threads:[~2002-01-28  0:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-27 16:06 Nathan Dorfman [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-01-27 17:45 rodrigc
2002-01-03 21:37 rodrigc
2001-05-03 13:06 nathan

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=20020128000600.22801.qmail@sources.redhat.com \
    --to=nathan@rtfm.net \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).