public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: David Miller <davem@davemloft.net>
Cc: lethal@linux-sh.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf tools: Kill off -Wcast-align
Date: Tue, 27 Oct 2009 14:50:25 +0100	[thread overview]
Message-ID: <20091027135025.GC32628@elte.hu> (raw)
In-Reply-To: <20091026.154055.07992945.davem@davemloft.net>


* David Miller <davem@davemloft.net> wrote:

> From: Paul Mundt <lethal@linux-sh.org>
> Date: Mon, 26 Oct 2009 18:47:30 +0900
> 
> > On Mon, Oct 26, 2009 at 07:25:20AM +0100, Ingo Molnar wrote:
> >> 
> >> * Paul Mundt <lethal@linux-sh.org> wrote:
> >> 
> >> > The present use of -Wcast-align causes the build to blow up on SH due to
> >> > generating a "cast increases required alignment of target type" error on
> >> > each invocation of list_for_each_entry().
> >> > 
> >> > It seems that this was previously reported and killed off in the ia64
> >> > support patch, but nothing seems to have happened with that. Presumably
> >> > the same problem still remains there, too.
> >> > 
> >> > Signed-off-by: Paul Mundt <lethal@linux-sh.org>
> >> 
> >> Is this a GCC bug producing false positive warnings? The GCC manpage 
> >> says:
> >> 
> >>        -Wcast-align
> >>            Warn whenever a pointer is cast such that the required alignment of the
> >>            target is increased.  For example, warn if a "char *" is cast to an
> >>            "int *" on machines where integers can only be accessed at two- or
> >>            four-byte boundaries.
> >> 
> >> Which looks moderately useful - if it works.
> >> 
> > Well, both ia64 and sh have hit this in the current compilers, and it
> > doesn't seem to pose any code generation issues. In the areas where it is
> > generated it seems to relate to 64-bit data types in the data structures,
> > which in itself doesn't seem inherently problematic.
> 
> sparc64 hits this too when building 32-bit perf binary, the first 
> thing I do after a pull is remove this warning option from the 
> Makefile :-)

Generally if you run into such issues in Sparc let us know so we can fix 
it :-)

Paul's fix is queued up for Linus.

	Ingo

  reply	other threads:[~2009-10-27 13:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-26  5:40 [PATCH] perf tools: Kill off -Wcast-align Paul Mundt
2009-10-26  6:25 ` Ingo Molnar
2009-10-26  9:47   ` Paul Mundt
2009-10-26 10:08     ` Pekka Enberg
2009-10-26 11:21       ` Ingo Molnar
2009-10-26 22:40     ` David Miller
2009-10-27 13:50       ` Ingo Molnar [this message]
2009-10-28  0:59         ` David Miller
2009-10-26 11:38 ` [tip:perf/urgent] perf tools: Remove -Wcast-align tip-bot for Paul Mundt

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=20091027135025.GC32628@elte.hu \
    --to=mingo@elte.hu \
    --cc=davem@davemloft.net \
    --cc=lethal@linux-sh.org \
    --cc=linux-kernel@vger.kernel.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