mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alessandro Suardi <alessandro.suardi@gmail.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.6.15-rc5-git3] hpet.c causes FC4 GCC 4.0.2 to bomb with unrecognizable insn
Date: Sat, 17 Dec 2005 21:50:29 +0100	[thread overview]
Message-ID: <5a4c581d0512171250j1572c086j4fa56c41d19fa0ae@mail.gmail.com> (raw)
In-Reply-To: <20051217123636.cdd53270.akpm@osdl.org>

On 12/17/05, Andrew Morton <akpm@osdl.org> wrote:
> Alessandro Suardi <alessandro.suardi@gmail.com> wrote:
> >
> >  CC      drivers/char/hpet.o
> > drivers/char/hpet.c: In function `hpet_calibrate':
> > drivers/char/hpet.c:803: Unrecognizable insn:
> > (insn/i 95 270 264 (parallel[
> >             (set (reg:SI 0 eax)
> >                 (asm_operands ("") ("=a") 0[
> >                         (reg:DI 1 edx)
> >                     ]
> >                     [
> >                         (asm_input:DI ("A"))
> >                     ]  ("drivers/char/hpet.c") 452))
> >             (set (reg:SI 1 edx)
> >                 (asm_operands ("") ("=d") 1[
> >                         (reg:DI 1 edx)
> >                     ]
> >                     [
> >                         (asm_input:DI ("A"))
> >                     ]  ("drivers/char/hpet.c") 452))
> >             (clobber (reg:QI 19 dirflag))
> >             (clobber (reg:QI 18 fpsr))
> >             (clobber (reg:QI 17 flags))
> >         ] ) -1 (insn_list 92 (nil))
> >     (nil))
> > drivers/char/hpet.c:803: confused by earlier errors, bailing out
> > make[2]: *** [drivers/char/hpet.o] Error 1
> > make[1]: *** [drivers/char] Error 2
> > make: *** [drivers] Error 2
> >
>
> Same compiler works OK here, so it's presumably "fixed" by some some good
> .config luck.
>
> If we can find a decent workaround in-kernel it's worth putting it in.
> It's quite possible that inlined hpet_time_div() - please try uninlining
> it.
>

Coincidence - I was about to post the fact that my earlier report
 was due to a pilot error (TM).

I had installed the compat-gcc packages due to legacy software
 which expected /usr/bin/gcc to be the FC2 2.96 GCC, then I
 forgot to point /usr/bin/gcc back to FC4 4.0.2 GCC.

So there is a compiler which bombs, but it's this one:

[asuardi@sandman ~]$ /usr/bin/gcc296 -v
Reading specs from /usr/lib/gcc-lib/i386-redhat-linux7/2.96/specs
gcc version 2.96 20000731 (Red Hat Linux 7.3 2.96-126)

Sorry for the false alarm about GCC 4.0.2. According to the
 current Documentation/Changes the 2.96 compiler seems to
 be expected to build these kernels, so perhaps there still is
 something to be looked into.

If anyone is interested I can try uninlining hpet_time_div()
 and rebuild with 2.96 then report back.

Thanks,

--alessandro

 "Somehow all you ever need is, never really quite enough, you know"

   (Bruce Springsteen - "Reno")

  reply	other threads:[~2005-12-17 20:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-13 13:07 Alessandro Suardi
2005-12-17 20:36 ` Andrew Morton
2005-12-17 20:50   ` Alessandro Suardi [this message]
2005-12-17 21:33     ` Adrian Bunk

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=5a4c581d0512171250j1572c086j4fa56c41d19fa0ae@mail.gmail.com \
    --to=alessandro.suardi@gmail.com \
    --cc=akpm@osdl.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

all inboxes | Powered by JetHome®