All of lore.kernel.org
 help / color / mirror / Atom feed
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:58:54 +0100	[thread overview]
Message-ID: <20121024135854.GD7339@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <CABYn4sz4v7Uf07am=MtPAKAvvAjwt+-bTRaLrBjoiRuyR9cfZw@mail.gmail.com>

On Wed, Oct 24, 2012 at 02:35:11PM +0100, Bastian Hecht wrote:
> 2012/10/24 Will Deacon <will.deacon@arm.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?
> 
> gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5)
> For a more verbose info take a look at the bug report link.

Ok, thanks. One other thing you could try while I try to find a copy of that
toolchain is changing the "+" modifier to an "=", like I proposed in this
version of the patch:

  http://lists.infradead.org/pipermail/linux-arm-kernel/2012-August/114971.html

Cheers,

Will

WARNING: multiple messages have this Message-ID (diff)
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: Possible regression in arm/io.h
Date: Wed, 24 Oct 2012 14:58:54 +0100	[thread overview]
Message-ID: <20121024135854.GD7339@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <CABYn4sz4v7Uf07am=MtPAKAvvAjwt+-bTRaLrBjoiRuyR9cfZw@mail.gmail.com>

On Wed, Oct 24, 2012 at 02:35:11PM +0100, Bastian Hecht wrote:
> 2012/10/24 Will Deacon <will.deacon@arm.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?
> 
> gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5)
> For a more verbose info take a look at the bug report link.

Ok, thanks. One other thing you could try while I try to find a copy of that
toolchain is changing the "+" modifier to an "=", like I proposed in this
version of the patch:

  http://lists.infradead.org/pipermail/linux-arm-kernel/2012-August/114971.html

Cheers,

Will

  reply	other threads:[~2012-10-24 13:58 UTC|newest]

Thread overview: 28+ 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:38 ` Bastian Hecht
2012-10-24 10:52 ` Will Deacon
2012-10-24 10:52   ` Will Deacon
2012-10-24 12:34   ` Bastian Hecht
2012-10-24 12:34     ` Bastian Hecht
2012-10-24 13:09     ` Will Deacon
2012-10-24 13:09       ` Will Deacon
2012-10-24 13:35       ` Bastian Hecht
2012-10-24 13:35         ` Bastian Hecht
2012-10-24 13:58         ` Will Deacon [this message]
2012-10-24 13:58           ` Will Deacon
2012-10-24 15:04           ` Bastian Hecht
2012-10-24 15:04             ` Bastian Hecht
2012-10-24 15:27             ` Will Deacon
2012-10-24 15:27               ` Will Deacon
2012-11-22  7:57               ` Artem Bityutskiy
2012-11-22  7:57                 ` Artem Bityutskiy
2012-11-22 10:19                 ` Will Deacon
2012-11-22 10:19                   ` Will Deacon
2012-11-22 10:23                   ` Artem Bityutskiy
2012-11-22 10:23                     ` Artem Bityutskiy
2012-10-25  6:55   ` Artem Bityutskiy
2012-10-25  6:55     ` Artem Bityutskiy
2012-10-25 11:17     ` Will Deacon
2012-10-25 11:17       ` Will Deacon
2012-10-25 12:35       ` Mikael Pettersson
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=20121024135854.GD7339@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.