* Huge cpp executables -- why?
@ 1999-02-25 22:40 Geoffrey T. Cheshire
[not found] ` < Pine.LNX.4.04.9902252322100.5058-100000@gches.goodnet.com >
1999-02-28 22:53 ` Geoffrey T. Cheshire
0 siblings, 2 replies; 8+ messages in thread
From: Geoffrey T. Cheshire @ 1999-02-25 22:40 UTC (permalink / raw)
To: egcs
Hello:
First the good news. I've successfully compiled and installed glibc-2.2
and the Linux 2.2.2 kernel on an i586 machine using the 1.1.2 pre 1
release. However, a hello world type C++ program produces a 400K
executable, even with -fno_exeptions -O.
size reports
text data bss dec hex filename
47069 15704 504 63277 f72d a.out
Is this expected?
Geoff
--
Geoffrey T. Cheshire <gches@goodnet.com>
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Huge cpp executables -- why?
[not found] ` < Pine.LNX.4.04.9902252322100.5058-100000@gches.goodnet.com >
@ 1999-02-26 0:29 ` Jeffrey A Law
1999-02-28 22:53 ` Jeffrey A Law
1999-02-26 7:39 ` H.J. Lu
1 sibling, 1 reply; 8+ messages in thread
From: Jeffrey A Law @ 1999-02-26 0:29 UTC (permalink / raw)
To: Geoffrey T. Cheshire; +Cc: egcs
In message < Pine.LNX.4.04.9902252322100.5058-100000@gches.goodnet.com >you wri
te:
> Hello:
>
> First the good news. I've successfully compiled and installed glibc-2.2
> and the Linux 2.2.2 kernel on an i586 machine using the 1.1.2 pre 1
> release. However, a hello world type C++ program produces a 400K
> executable, even with -fno_exeptions -O.
>
> size reports
>
> text data bss dec hex filename
> 47069 15704 504 63277 f72d a.out
>
> Is this expected?
If the image is 400k, but the sizes you've show above are accurate, then
either you symbol table is really big, or you have debugging information
in your executable.
Neither of which actually effect the runtime behavior of the program.
jeff
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Huge cpp executables -- why?
[not found] ` < Pine.LNX.4.04.9902252322100.5058-100000@gches.goodnet.com >
1999-02-26 0:29 ` Jeffrey A Law
@ 1999-02-26 7:39 ` H.J. Lu
[not found] ` < m10GPMo-000390C@ocean.lucon.org >
1999-02-28 22:53 ` H.J. Lu
1 sibling, 2 replies; 8+ messages in thread
From: H.J. Lu @ 1999-02-26 7:39 UTC (permalink / raw)
To: Geoffrey T. Cheshire; +Cc: egcs
>
> Hello:
>
> First the good news. I've successfully compiled and installed glibc-2.2
> and the Linux 2.2.2 kernel on an i586 machine using the 1.1.2 pre 1
> release. However, a hello world type C++ program produces a 400K
> executable, even with -fno_exeptions -O.
>
> size reports
>
> text data bss dec hex filename
> 47069 15704 504 63277 f72d a.out
>
> Is this expected?
>
Did you configure egcs with --enable-threads --enable-shared? I think
they should be default for glibc 2 on Linux. Otherwise, you may not
run C++ binaries compiled on other Linux boxes.
--
H.J. Lu (hjl@gnu.org)
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Huge cpp executables -- why?
[not found] ` < m10GPMo-000390C@ocean.lucon.org >
@ 1999-02-26 14:03 ` Geoffrey T. Cheshire
1999-02-28 22:53 ` Geoffrey T. Cheshire
0 siblings, 1 reply; 8+ messages in thread
From: Geoffrey T. Cheshire @ 1999-02-26 14:03 UTC (permalink / raw)
To: H.J. Lu; +Cc: egcs
On Fri, 26 Feb 1999, H.J. Lu wrote:
> Did you configure egcs with --enable-threads --enable-shared? I think
> they should be default for glibc 2 on Linux. Otherwise, you may not
> run C++ binaries compiled on other Linux boxes.
I explicitly configured with --enable-threads; I thought --enable-shared
was by default (as you say), but I'll have to go back and make sure that
really happened.
Thanks,
Geoff
--
Geoffrey T. Cheshire <gches@goodnet.com>
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Huge cpp executables -- why?
1999-02-26 7:39 ` H.J. Lu
[not found] ` < m10GPMo-000390C@ocean.lucon.org >
@ 1999-02-28 22:53 ` H.J. Lu
1 sibling, 0 replies; 8+ messages in thread
From: H.J. Lu @ 1999-02-28 22:53 UTC (permalink / raw)
To: Geoffrey T. Cheshire; +Cc: egcs
>
> Hello:
>
> First the good news. I've successfully compiled and installed glibc-2.2
> and the Linux 2.2.2 kernel on an i586 machine using the 1.1.2 pre 1
> release. However, a hello world type C++ program produces a 400K
> executable, even with -fno_exeptions -O.
>
> size reports
>
> text data bss dec hex filename
> 47069 15704 504 63277 f72d a.out
>
> Is this expected?
>
Did you configure egcs with --enable-threads --enable-shared? I think
they should be default for glibc 2 on Linux. Otherwise, you may not
run C++ binaries compiled on other Linux boxes.
--
H.J. Lu (hjl@gnu.org)
^ permalink raw reply [flat|nested] 8+ messages in thread
* Huge cpp executables -- why?
1999-02-25 22:40 Huge cpp executables -- why? Geoffrey T. Cheshire
[not found] ` < Pine.LNX.4.04.9902252322100.5058-100000@gches.goodnet.com >
@ 1999-02-28 22:53 ` Geoffrey T. Cheshire
1 sibling, 0 replies; 8+ messages in thread
From: Geoffrey T. Cheshire @ 1999-02-28 22:53 UTC (permalink / raw)
To: egcs
Hello:
First the good news. I've successfully compiled and installed glibc-2.2
and the Linux 2.2.2 kernel on an i586 machine using the 1.1.2 pre 1
release. However, a hello world type C++ program produces a 400K
executable, even with -fno_exeptions -O.
size reports
text data bss dec hex filename
47069 15704 504 63277 f72d a.out
Is this expected?
Geoff
--
Geoffrey T. Cheshire <gches@goodnet.com>
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Huge cpp executables -- why?
1999-02-26 0:29 ` Jeffrey A Law
@ 1999-02-28 22:53 ` Jeffrey A Law
0 siblings, 0 replies; 8+ messages in thread
From: Jeffrey A Law @ 1999-02-28 22:53 UTC (permalink / raw)
To: Geoffrey T. Cheshire; +Cc: egcs
In message < Pine.LNX.4.04.9902252322100.5058-100000@gches.goodnet.com >you wri
te:
> Hello:
>
> First the good news. I've successfully compiled and installed glibc-2.2
> and the Linux 2.2.2 kernel on an i586 machine using the 1.1.2 pre 1
> release. However, a hello world type C++ program produces a 400K
> executable, even with -fno_exeptions -O.
>
> size reports
>
> text data bss dec hex filename
> 47069 15704 504 63277 f72d a.out
>
> Is this expected?
If the image is 400k, but the sizes you've show above are accurate, then
either you symbol table is really big, or you have debugging information
in your executable.
Neither of which actually effect the runtime behavior of the program.
jeff
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Huge cpp executables -- why?
1999-02-26 14:03 ` Geoffrey T. Cheshire
@ 1999-02-28 22:53 ` Geoffrey T. Cheshire
0 siblings, 0 replies; 8+ messages in thread
From: Geoffrey T. Cheshire @ 1999-02-28 22:53 UTC (permalink / raw)
To: H.J. Lu; +Cc: egcs
On Fri, 26 Feb 1999, H.J. Lu wrote:
> Did you configure egcs with --enable-threads --enable-shared? I think
> they should be default for glibc 2 on Linux. Otherwise, you may not
> run C++ binaries compiled on other Linux boxes.
I explicitly configured with --enable-threads; I thought --enable-shared
was by default (as you say), but I'll have to go back and make sure that
really happened.
Thanks,
Geoff
--
Geoffrey T. Cheshire <gches@goodnet.com>
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~1999-02-28 22:53 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1999-02-25 22:40 Huge cpp executables -- why? Geoffrey T. Cheshire
[not found] ` < Pine.LNX.4.04.9902252322100.5058-100000@gches.goodnet.com >
1999-02-26 0:29 ` Jeffrey A Law
1999-02-28 22:53 ` Jeffrey A Law
1999-02-26 7:39 ` H.J. Lu
[not found] ` < m10GPMo-000390C@ocean.lucon.org >
1999-02-26 14:03 ` Geoffrey T. Cheshire
1999-02-28 22:53 ` Geoffrey T. Cheshire
1999-02-28 22:53 ` H.J. Lu
1999-02-28 22:53 ` Geoffrey T. Cheshire
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).