public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Alex Bradbury <asb@asbradbury.org>
To: Palmer Dabbelt <palmer@dabbelt.com>
Cc: binutils@sourceware.org
Subject: Re: [PATCH] RISC-V: Allow ISA subsets to be disabled
Date: Fri, 31 Mar 2017 08:15:00 -0000	[thread overview]
Message-ID: <CA+wH2959nxF6PZDYJC1LfT2WVt8t8o64qPfQQCh1o9mS+LDT3w@mail.gmail.com> (raw)
In-Reply-To: <20170330194542.10927-1-palmer@dabbelt.com>

On 30 March 2017 at 20:45, Palmer Dabbelt <palmer@dabbelt.com> wrote:
> Without this patch, passing "-march=rv64ic -march=rv64i" results in
> you getting a "RV64IC" toolchain, which isn't expected.
>
> gas/ChangeLog:
>
> 2017-03-30  Palmer Dabbelt  <palmer@dabbelt.com>
>
>        * config/tc-riscv.c (riscv_clear_subsets): New function.
>        (riscv_add_subset): Call riscv_clear_subsets and riscv_set_rvc to
>        clear RVC when it's been previously set.

For what it's worth, the current behaviour (i.e. the behaviour before
this patch) seems to be in line with other architectures. e.g. if I do
`gcc -march=native -march=generic` then the latter won't override the
former - at least as evidenced by `gcc -march=native -march=generic -E
-v - </dev/null`.

Best,

Alex

  reply	other threads:[~2017-03-31  8:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-30 19:46 Palmer Dabbelt
2017-03-31  8:15 ` Alex Bradbury [this message]
2017-03-31  8:39   ` Alex Bradbury
2017-03-31  9:23     ` Nick Clifton
2017-03-31 16:46       ` Palmer Dabbelt
2017-03-31  9:09 ` Nick Clifton
2017-04-01 10:50 ` [BUILDROBOT] RISC-V: error: passing argument 1 of ‘free’ discards ‘const’ qualifier from pointer target type (was: [PATCH] RISC-V: Allow ISA subsets to be disabled) Jan-Benedict Glaw

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=CA+wH2959nxF6PZDYJC1LfT2WVt8t8o64qPfQQCh1o9mS+LDT3w@mail.gmail.com \
    --to=asb@asbradbury.org \
    --cc=binutils@sourceware.org \
    --cc=palmer@dabbelt.com \
    /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).