From: Holger Burkarth <burkarth@prodad.de>
To: gnu-win32@cygnus.com
Subject: Gcc
Date: Sun, 29 Nov 1998 01:32:00 -0000 [thread overview]
Message-ID: <yam7637.1925.136553584@mail.toplink.net> (raw)
Hi,
i have a little question, the normaly so good
gcc machine-code, is in any case not
so good, what is the reason ?
------ Source -------
void test2()
{
const char* Tst="";
if(Tst != NULL) printf(Tst);
}
$ gcc main.cpp -O2 -S
------ Output -------
.file"main.cc"
# GNU C++ version egcs-2.91.57 19980901 (egcs-1.1 release)
# (i686-pc-cygwin32) compiled by GNU C version egcs-2.91.57 19980901
# (egcs-1.1 release).
# options passed: -mcpu=i486 -mno-stack-arg-probe -O2 -Wchar-subscripts
# -Wcomment -Wimplicit -Wparentheses -Wreturn-type -Wunused
# -Wuninitialized -Wshadow -Wwrite-strings -Waggregate-return -Winline
# -fno-exceptions -fomit-frame-pointer -fverbose-asm
# options enabled: -fdefer-pop -fomit-frame-pointer -fcse-follow-jumps
# -fcse-skip-blocks -fexpensive-optimizations -fthread-jumps
# -fstrength-reduce -fpeephole -fforce-mem -ffunction-cse -finline
# -fkeep-static-consts -fcaller-saves -freg-struct-return -fgcse
# -frerun-cse-after-loop -frerun-loop-opt -fschedule-insns2
# -fsjlj-exceptions -fcommon -fverbose-asm -fgnu-linker -fregmove
# -foptimize-register-move -fargument-alias -m80387 -mhard-float
# -mno-soft-float -mieee-fp -mfp-ret-in-387 -mschedule-prologue -mcpu=i686
# -march=pentium
gcc2_compiled.:
___gnu_compiled_cplusplus:
.text
LC0:
.ascii "\0"
.globl _Test2__Fv
_Test2__Fv:
movl $LC0,%eax
testl %eax,%eax
je L138 <- why this ?
pushl %eax
call _printf
addl $4,%esp
L138:
ret
--
Holger Burkarth
Software-Developer
burkarth@prodad.de
http://www.prodad.de
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
next reply other threads:[~1998-11-29 1:32 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-11-29 1:32 Holger Burkarth [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-08-18 11:56 GCC John Emmas
2008-08-18 12:11 ` GCC Hugh Sasse
2008-08-18 12:20 ` GCC John Emmas
2002-05-25 9:46 gcc hongxun lee
2002-01-02 9:14 gcc Givon Zirkind
2002-01-03 16:21 ` gcc Tim Prince
2001-05-07 17:49 gcc Bryan Higgins
2001-05-08 6:00 ` gcc Earnie Boyd
2001-03-31 11:06 gcc John Weeks
2001-03-31 13:06 ` gcc Christopher Faylor
2001-03-31 14:14 ` gcc John Weeks
2001-03-31 14:24 ` gcc Christopher Faylor
2000-11-09 11:01 GCC Earnie Boyd
2000-11-09 7:19 GCC Schaible, Joerg
2000-11-09 7:13 GCC Milan Stanojevic
2000-11-09 7:19 ` GCC Cal Erickson
2000-11-09 10:45 ` GCC Milan Stanojevic
1999-09-14 5:48 GCC Earnie Boyd
1999-09-14 6:54 ` GCC Kai Henningsen
1999-09-30 23:42 ` GCC Kai Henningsen
1999-09-30 23:42 ` GCC Earnie Boyd
1999-09-13 8:16 GCC Earnie Boyd
1999-09-14 2:00 ` GCC Kai Henningsen
1999-09-14 9:56 ` GCC Michael V. Nikolaev
1999-09-30 23:42 ` GCC Michael V. Nikolaev
1999-09-30 23:42 ` GCC Kai Henningsen
1999-09-30 23:42 ` GCC Earnie Boyd
1999-08-23 8:50 GCC hark sng-
1999-08-23 9:59 ` GCC Mumit Khan
1999-08-31 23:49 ` GCC Mumit Khan
1999-09-13 8:01 ` GCC Kai Henningsen
1999-09-13 8:54 ` GCC Mumit Khan
1999-09-14 1:54 ` GCC Kai Henningsen
1999-09-14 9:41 ` GCC Mumit Khan
1999-09-30 23:42 ` GCC Mumit Khan
1999-09-30 23:42 ` GCC Kai Henningsen
1999-09-30 23:42 ` GCC Mumit Khan
1999-09-30 23:42 ` GCC Kai Henningsen
1999-08-31 23:49 ` GCC hark sng-
1998-11-29 10:34 Gcc Haynes, Dan
1998-11-03 13:49 gcc marc_auslander
1998-07-08 10:01 GCC Earnie Boyd
1998-07-03 16:33 GCC Bruno da Rocha
1997-12-05 6:13 gcc Mark Young (in6)
1997-10-16 20:09 GCC Earnie Boyd
1997-10-15 17:59 GCC David Vang
1997-10-08 2:57 gcc Brad Haack
1997-09-24 2:09 gcc nazg
1997-09-23 13:38 gcc Earnie Boyd
1997-09-22 9:29 gcc Earnie Boyd
1997-09-22 6:23 gcc nazg
1997-09-20 0:35 gcc young lee
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=yam7637.1925.136553584@mail.toplink.net \
--to=burkarth@prodad.de \
--cc=gnu-win32@cygnus.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).