linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Laura Abbott <labbott@redhat.com>
To: Will Deacon <will.deacon@arm.com>
Cc: Masahiro Yamada <yamada.masahiro@socionext.com>,
	Ard Biesheuvel <ard.biesheuvel@linaro.org>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	Andrew.Murray@arm.com
Subject: Re: CONFIG_OPTIMIZE_INLINING breaks atomic64 test on arm64
Date: Tue, 11 Jun 2019 12:13:10 -0400	[thread overview]
Message-ID: <f349b8ee-6df6-ee4e-615e-6b0a2e8eb3ec@redhat.com> (raw)
In-Reply-To: <20190611155025.GI4324@fuggles.cambridge.arm.com>

On 6/11/19 11:50 AM, Will Deacon wrote:
> Hi Laura,
> 
> On Wed, May 29, 2019 at 12:30:00PM +0100, Will Deacon wrote:
>> On Tue, May 28, 2019 at 05:42:04PM -0400, Laura Abbott wrote:
>>> CONFIG_OPTIMIZE_INLINING is a selectable option on arm64 now. It currently
>>> triggers a bug on the CONFIG_ATOMIC64_SELFTEST:
>>
>> At this point, I'd be inclined to raise something in the GCC bugzilla
>> with the result of --save-temps for the failing atomic64_test.c. Maybe
>> they will have a better opinion as to whether we're doing something wrong
>> here. Is that something you're willing to do, or shall I do it?
> 
> Did you file a GCC bugzilla entry for this, or shall I go ahead and make
> a new one (assuming I can remember my credentials for that thing)?
> 
> Will
> 

I didn't file one, if you already have the account I'm happy to let you
do that since I don't actually have one (maybe I should though at the
rate I seem to stumble across bugs...)

Thanks,
Laura

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      reply	other threads:[~2019-06-11 16:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-28 21:42 CONFIG_OPTIMIZE_INLINING breaks atomic64 test on arm64 Laura Abbott
2019-05-29 11:21 ` Mark Rutland
2019-05-29 11:28   ` Mark Rutland
2019-05-29 11:29 ` Will Deacon
2019-05-29 11:53   ` Russell King - ARM Linux admin
2019-06-11 15:50   ` Will Deacon
2019-06-11 16:13     ` Laura Abbott [this message]

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=f349b8ee-6df6-ee4e-615e-6b0a2e8eb3ec@redhat.com \
    --to=labbott@redhat.com \
    --cc=Andrew.Murray@arm.com \
    --cc=ard.biesheuvel@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=will.deacon@arm.com \
    --cc=yamada.masahiro@socionext.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 NNTP newsgroup(s).