From: David Miller <davem@davemloft.net>
To: ebotcazou@adacore.com
Cc: gcc-patches@gcc.gnu.org, sebastian.huber@embedded-brains.de,
cederman@gaisler.com, daniel@gaisler.com
Subject: Re: [PATCH] [SPARC] Add a workaround for the LEON3FT store-store errata
Date: Tue, 20 Jun 2017 19:54:00 -0000 [thread overview]
Message-ID: <20170620.155425.2221282257163468716.davem@davemloft.net> (raw)
In-Reply-To: <4541598.kZ55kCGA8h@polaris>
From: Eric Botcazou <ebotcazou@adacore.com>
Date: Tue, 20 Jun 2017 21:19:37 +0200
>> I'm fine with this change.
>
> I disagree, the existing policy is to avoid switches like -mfix-b2bst and use
> -mfix-xxxx where xxxx is a CPU (here xxxx could be ut699e or ut700).
Ok, I was not aware of that policy. But this should be easy for the
submitter to fix.
next prev parent reply other threads:[~2017-06-20 19:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-14 8:26 Daniel Cederman
2017-06-20 5:55 ` Sebastian Huber
2017-06-20 15:44 ` David Miller
2017-06-20 19:19 ` Eric Botcazou
2017-06-20 19:54 ` David Miller [this message]
2017-06-21 6:35 ` Eric Botcazou
2017-06-21 13:28 Daniel Cederman
2017-06-22 14:06 ` David Miller
2017-06-26 7:22 ` Eric Botcazou
2017-06-27 8:52 ` Daniel Cederman
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=20170620.155425.2221282257163468716.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=cederman@gaisler.com \
--cc=daniel@gaisler.com \
--cc=ebotcazou@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=sebastian.huber@embedded-brains.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).