All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Joel Soete" <jsoe0708@tiscali.be>
To: "John David Anglin" <dave@hiauly1.hia.nrc.ca>, joel.soete@tiscali.be
Cc: xam@cs.ucc.ie, parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] compiler & kernel
Date: Tue, 3 Jun 2003 09:14:40 +0200	[thread overview]
Message-ID: <3ED70CF100001190@ocpmta2.freegates.net> (raw)
In-Reply-To: <200306021732.h52HWKNp010654@hiauly1.hia.nrc.ca>

>-- Original Message --
>Subject: Re: [parisc-linux] compiler & kernel
>To: joel.soete@tiscali.be (Joel Soete)
>Date: Mon, 2 Jun 2003 13:32:20 -0400 (EDT)
>From: "John David Anglin" <dave@hiauly1.hia.nrc.ca>
>Cc: xam@cs.ucc.ie, parisc-linux@lists.parisc-linux.org
>
>
>> >hppa64-gcc (3.2.3, from ftp.p-l.org unofficial-debs)
> >  seems to work fine but obviously ipt_limit.o is miscompiled:
> >  I can insmod it, but iptable wouldn't recognize the --limit* options.
> >  There are still some problems with some modules
>and canonicalize_funcptr,
> >
> Are you sure this is with hppa64-gcc (iirc canonicalize.., was just 
> recently backport to 3.2)?

> hppa64-gcc does not canonicalize function pointers.

Thanks to confirm (without my full mb I was not quiet sure of my memory :)
)


> >  Man, gcc-3.3 is SLOW! it takes ages to compile the kerne
>!

> I suspect this is related to changes in the inlining model.  This is
> definitely a problem with certain C++ applications. 

I did not observe this behaviour on my b180 b2k or N with gcc-3.3 to compile
various _kernel_ (not C++) 2.4.20 or 2.4.21  (just always anoying canonicalize_
pb and execpted (void *) cast work-around for builtin function, I do not
yet find an easy way to solved module pb)

btw I notice another difference between 32bits and 64bits kernels:
# file vmlinux-2.4.21-rc6-pa35
vmlinux-2.4.21-rc6-pa35: ELF 32-bit MSB ..., statically linked, not stripped

# file vmlinux-2.4.21-rc4-pa35
vmlinux-2.4.21-rc4-pa35: ELF 64-bit MSB ..., dynamically linked (uses share
libs), ...

In the 32-bits case I well understand that kernel was staticaly linked but
I but surprised that 64-bit kernel is dynamically linked? 


> If anybody can
> generate profile and/or pass timing data for 3.3 versus 3.0.4, I
> would like to see them.

Anyway could you let me know how to 'generate this profile'


Thanks for attention,
    Joel

---------------------------------
Découvrez les 6 clés et gagnez le Club Med à Vie avec Tiscali
http://www.tiscali.be/nl/subs/tiscali4life/default.asp?lang=fr

  reply	other threads:[~2003-06-03  7:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-30 12:10 [parisc-linux] compiler & kernel M. Grabert
2003-05-31 10:40 ` Joel Soete
2003-06-02  8:10   ` M. Grabert
2003-06-02 17:32   ` John David Anglin
2003-06-03  7:14     ` Joel Soete [this message]
2003-06-03 14:18       ` John David Anglin
2003-06-03 15:35         ` Joel Soete
2003-06-03 23:59         ` Grant Grundler
2003-06-04  5:47           ` John David Anglin
  -- strict thread matches above, loose matches on Subject: below --
2003-06-02 10:11 Joel Soete
2003-06-02 19:05 ` Matthias Klose
2003-06-02 20:20 ` M. Grabert
2003-06-02 21:58   ` Grant Grundler
2003-06-03 17:21 Joel Soete

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=3ED70CF100001190@ocpmta2.freegates.net \
    --to=jsoe0708@tiscali.be \
    --cc=dave@hiauly1.hia.nrc.ca \
    --cc=joel.soete@tiscali.be \
    --cc=parisc-linux@lists.parisc-linux.org \
    --cc=xam@cs.ucc.ie \
    /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.