public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: ebotcazou@adacore.com
Cc: gcc-patches@gcc.gnu.org, ro@cebitec.uni-bielefeld.de
Subject: Re: [PATCH v3] Add support for sparc compare-and-branch
Date: Tue, 13 Nov 2012 19:41:00 -0000	[thread overview]
Message-ID: <20121113.144058.1489444750556522789.davem@davemloft.net> (raw)
In-Reply-To: <1967849.TQiz8OpHdv@polaris>

From: Eric Botcazou <ebotcazou@adacore.com>
Date: Tue, 13 Nov 2012 20:32:40 +0100

> Working on this, I discovered an oddity in GNU as: -xarch=sparc4 -64 yields a 
> 64-bit object file whereas -64 -xarch=sparc4 yields a 32-bit object file.  My 
> understanding is that Sun as will generate a 64-bit object file in both cases.

Thanks for finding this, that's definitely incorrect behavior.  I bet there
is some unintended override triggered by sparc4 selection, and I'll go and
fix that soon.

  reply	other threads:[~2012-11-13 19:41 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-23  4:55 David Miller
2012-10-25 18:28 ` David Miller
2012-10-26  9:23   ` Rainer Orth
2012-11-13  2:46     ` David Miller
2012-11-15 14:29       ` Rainer Orth
2012-10-26  9:13 ` Eric Botcazou
2012-10-26  9:31   ` David Miller
2012-11-11 22:30 ` Eric Botcazou
2012-11-11 23:16   ` David Miller
2012-11-12  8:38     ` Eric Botcazou
2012-11-12 14:39       ` Rainer Orth
2012-11-12 15:37         ` Eric Botcazou
2012-11-12 15:46           ` Rainer Orth
2012-11-12 19:35             ` David Miller
2012-11-13 19:34               ` Eric Botcazou
2012-11-13 19:41                 ` David Miller [this message]
2012-11-13 21:52                   ` Eric Botcazou
2012-11-13 21:58                     ` David Miller
2012-11-12 19:37       ` David Miller
2012-11-12 17:56 ` Richard Henderson
2012-11-12 19:38   ` David Miller

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=20121113.144058.1489444750556522789.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=ebotcazou@adacore.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=ro@cebitec.uni-bielefeld.de \
    /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).