From: Will Deacon <will.deacon@arm.com>
To: Bastian Hecht <hechtb@googlemail.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Artem Bityutskiy <dedekind1@gmail.com>
Subject: Re: Possible regression in arm/io.h
Date: Wed, 24 Oct 2012 14:09:57 +0100 [thread overview]
Message-ID: <20121024130957.GB7339@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <CABYn4swp9JBEHgGTOkoe=tOh3Mf1dq5WYr=2xuKNpTmLX5LcFQ@mail.gmail.com>
On Wed, Oct 24, 2012 at 01:34:18PM +0100, Bastian Hecht wrote:
> 2012/10/24 Will Deacon <will.deacon@arm.com>:
> > It sounds like we need to:
> >
> > (a) Understand what has changed in GCC to cause this error to start
> > cropping up.
> >
> > (b) Have a look at the impact of using only "Q" on the generated
> > code (especially register usage for the address).
> >
>
> Uff... I've just started to write ARM assembly and have no practical
> experience with the inner workings of real world compilers. So this
> time I'm afraid I was just good enough to report this. It sounds
> interesting to hunt it, but would take ages for me at this point.
Ok, I'll have a look at the impact of moving exclusively to "Q" when I get a
chance. Which toolchain are you using?
Will
next prev parent reply other threads:[~2012-10-24 13:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-24 10:38 Possible regression in arm/io.h Bastian Hecht
2012-10-24 10:52 ` Will Deacon
2012-10-24 12:34 ` Bastian Hecht
2012-10-24 13:09 ` Will Deacon [this message]
2012-10-24 13:35 ` Bastian Hecht
2012-10-24 13:58 ` Will Deacon
2012-10-24 15:04 ` Bastian Hecht
2012-10-24 15:27 ` Will Deacon
2012-11-22 7:57 ` Artem Bityutskiy
2012-11-22 10:19 ` Will Deacon
2012-11-22 10:23 ` Artem Bityutskiy
2012-10-25 6:55 ` Artem Bityutskiy
2012-10-25 11:17 ` Will Deacon
2012-10-25 12:35 ` Mikael Pettersson
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=20121024130957.GB7339@mudshark.cambridge.arm.com \
--to=will.deacon@arm.com \
--cc=dedekind1@gmail.com \
--cc=hechtb@googlemail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mtd@lists.infradead.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