public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Marcus Shawcroft <marcus.shawcroft@gmail.com>
To: Yvan Roux <yvan.roux@linaro.org>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
	Maxim Kuvyrkov <maxim.kuvyrkov@linaro.org>,
		Richard Earnshaw <Richard.Earnshaw@arm.com>,
	James Greenhalgh <james.greenhalgh@arm.com>
Subject: Re: [PATCH, AArch64] Add Cortex-A53 erratum 843419 configure-time option
Date: Fri, 01 May 2015 11:11:00 -0000	[thread overview]
Message-ID: <CAFqB+PzJmQo25P1NR8cfA814EoeSquPYE5Vt_8mhU9Xctm_AAQ@mail.gmail.com> (raw)
In-Reply-To: <CAD57uCdGEc4PH=V4DQpTVuCvTSJx35pvS_yAE_vQGmUYRDrZBA@mail.gmail.com>

On 1 May 2015 at 10:11, Yvan Roux <yvan.roux@linaro.org> wrote:
> Hi all,
>
> As described in the thread bellow, there is a link-time workaround for
> an erratum (843419) of some early revision of Cortex-A53.  Similarly
> to what was done for a previous erratum, this patch adds a new
> configure-time option --enable-fix-cortex-a53-843419 that pass down
> the linker option --fix-cortex-a53-843419.
>
> I haven't implemented flags to explicitly disable/enable it during
> compilation as it is only a linker workaround, but I can do it if you
> think it's necessary.

Hi Yvan,

In the case of the 835769 erratum, providing such GCC configury made
(some) sense because the workaround included both a GCC and an LD
component. GCC in effect needed the option to control GCC behaviour
aswell as LD behaviour. The same is not true of 843419. The net effect
of the proposed  patch here is to provide a configure option in GCC to
change the default behaviour of LD, with no other purpose within GCC
itself.  This seems rather bizarre to me. I would have thought that if
the sole objective is to change the default behaviour of LD, then
there should be configure time options on LD, rather than GCC.

That said, I can also see that providing consistent behaviour across
these various work around configure options and consistent run time
options for the user will reduce confusion in the future, both for
folks building toolchains and for the folks using them.  From this
perspective I think it would be better to go with this patch *and*
include the flags explicitly such the both of the current workaround
have equivalent configury behaviour and have equivalent user flags at
run time.

Cheers
/Marcus

>
> https://sourceware.org/ml/binutils-cvs/2015-04/msg00012.html
>
> Is it ok for trunk and/or branches ?
>
> Thanks,
> Yvan
>
> 2015-05-01  Yvan Roux  <yvan.roux@linaro.org>
>
>     * configure.ac: Add --enable-fix-cortex-a53-843419 option.
>     * configure: Regenerate.
>     * config/aarch64/aarch64-elf-raw.h (CA53_ERR_843419_SPEC): Define.
>     (LINK_SPEC): Include CA53_ERR_843419_SPEC.
>     * config/aarch64/aarch64-linux.h (CA53_ERR_843419_SPEC): Define.
>     (LINK_SPEC): Include CA53_ERR_843419_SPEC.
>     * doc/install.texi (aarch64*-*-*): Document
>     new --enable-fix-cortex-a53-843419 option.

  reply	other threads:[~2015-05-01 11:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-01  9:11 Yvan Roux
2015-05-01 11:11 ` Marcus Shawcroft [this message]
2015-05-01 11:39   ` Yvan Roux
2015-05-01 13:56     ` Yvan Roux
2015-05-01 15:18       ` Marcus Shawcroft
2015-05-04  8:59         ` Yvan Roux
2015-05-05  8:11           ` Marcus Shawcroft
2015-05-12  9:06             ` Yvan Roux

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=CAFqB+PzJmQo25P1NR8cfA814EoeSquPYE5Vt_8mhU9Xctm_AAQ@mail.gmail.com \
    --to=marcus.shawcroft@gmail.com \
    --cc=Richard.Earnshaw@arm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=james.greenhalgh@arm.com \
    --cc=maxim.kuvyrkov@linaro.org \
    --cc=yvan.roux@linaro.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).