public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: "Jan Beulich" <jbeulich@novell.com>
Cc: "Jiri Kosina" <jikos@jikos.cz>, linux-kernel@vger.kernel.org
Subject: Re: dwarf2 stuck Re: lockdep warning in i2c_transfer() with dibx000 DVB - input tree merge plans?
Date: Mon, 16 Oct 2006 16:17:51 +0200	[thread overview]
Message-ID: <200610161617.51111.ak@suse.de> (raw)
In-Reply-To: <4533A5A5.76E4.0078.0@novell.com>

On Monday 16 October 2006 15:30, Jan Beulich wrote:
> >>> Jiri Kosina <jikos@jikos.cz> 16.10.06 15:08 >>>
> >On Mon, 16 Oct 2006, Jan Beulich wrote:
> >
> >> >Yes, it was compiled using gcc 4.0.2, specifically gcc (GCC) 4.0.2 
> >> >20051125 (Red Hat 4.0.2-8). I can easily reproduce this, what 
> >> >additional information do you need? Or should I just try with newer 
> >> >gcc?
> >> Two possible paths:
> >> a) Try with gcc 4.1.x.
> >
> >Will do probably later today.
> >
> >> b) Send me the offending .o (presumably the one containing 
> >> dibusb_dib3000mc_tuner_attach)
> >
> >You can get it from http://www.jikos.cz/jikos/junk/dibusb-common.o 
> 
> Yes, unfortunately this is another instance of gcc 4.0 generating bad
> unwind data when optimizing and not accumulating outgoing args.
> Andi - did you already create a patch implementing Michael's suggestion?

You mean using -maccumulate-outgoing-args ? Not yet.

I guess we can do it unconditionally for all gccs on both i386
and x86-64, right?

-Andi

  reply	other threads:[~2006-10-16 14:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-12 13:33 lockdep warning in i2c_transfer() with dibx000 DVB - input tree merge plans? Jiri Kosina
2006-10-13  2:37 ` Dmitry Torokhov
2006-10-13  6:13 ` Ingo Molnar
2006-10-16 10:31 ` dwarf2 stuck " Andi Kleen
2006-10-16 12:37   ` Jan Beulich
2006-10-16 12:45     ` Jiri Kosina
2006-10-16 12:59       ` Jan Beulich
2006-10-16 13:08         ` Jiri Kosina
2006-10-16 13:30           ` Jan Beulich
2006-10-16 14:17             ` Andi Kleen [this message]
2006-10-16 14:24               ` Jan Beulich
2006-10-16 14:34                 ` Andi Kleen

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=200610161617.51111.ak@suse.de \
    --to=ak@suse.de \
    --cc=jbeulich@novell.com \
    --cc=jikos@jikos.cz \
    --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