mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Thomas Gleixner <tglx@www.tglx.de>,
	Pierre Ossman <drzeus-list@drzeus.cx>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: Fedora's latest gcc produces unbootable kernels
Date: Mon, 3 Dec 2007 13:03:28 +0100 (CET)	[thread overview]
Message-ID: <alpine.LFD.0.9999.0712031302280.6765@localhost.localdomain> (raw)
In-Reply-To: <20071203115112.GT16835@devserv.devel.redhat.com>

On Mon, 3 Dec 2007, Jakub Jelinek wrote:

> On Mon, Dec 03, 2007 at 12:34:17PM +0100, Thomas Gleixner wrote:
> > Of course just to annoy you :)
> 
> It doesn't matter whether I'm annoyed about this or not, but whether gcc is
> able to generate decent code with it or not.  And especially with union it
> is not, at least through all the tree ssa passes.  You already have a lot of
> the details hidden in ktime.h accessor inlines, so I don't think it would be
> hard to add further one or two.
> 
> Anyway, even just using typedef struct ktime { s64 tv64; } ktime_t; could
> make things better in case you have just one field.  Unlike unions, structs
> can be (and in this case most likely will be) scalarized by SRA, so
> half of tree SSA passes will see it as integral var and will be able to
> perform optimizations on it.

Makes sense. I look into fixing that.

Thanks,

	tglx

      reply	other threads:[~2007-12-03 12:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-01 14:42 Pierre Ossman
2007-12-01 17:47 ` Pierre Ossman
2007-12-01 18:37   ` Bill Davidsen
2007-12-01 20:11     ` Pierre Ossman
2007-12-01 20:20   ` Pierre Ossman
2007-12-03  8:17     ` Thomas Gleixner
2007-12-03  8:58       ` Jakub Jelinek
2007-12-03 11:34         ` Thomas Gleixner
2007-12-03 11:51           ` Jakub Jelinek
2007-12-03 12:03             ` Thomas Gleixner [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=alpine.LFD.0.9999.0712031302280.6765@localhost.localdomain \
    --to=tglx@linutronix.de \
    --cc=drzeus-list@drzeus.cx \
    --cc=jakub@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@www.tglx.de \
    /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

Powered by JetHome