From: Chris Friesen <cfriesen@nortelnetworks.com>
To: Jesper Juhl <juhl-lkml@dif.dk>
Cc: Jan Engelhardt <jengelh@linux01.gwdg.de>,
Oliver Neukum <oliver@neukum.org>,
Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: question on common error-handling idiom
Date: Wed, 03 Nov 2004 10:49:19 -0600 [thread overview]
Message-ID: <41890C0F.6080702@nortelnetworks.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0411022241160.3285@dragon.hygekrogen.localhost>
Jesper Juhl wrote:
> Has anyone taken a look at what recent gcc's actually do with different
> variations of the constructs mentioned in this thread?
I did, out of curiosity:
I used the following (admittedly simplistic) code, compiled with -O2.
int bbbb(int a)
{
int err = -5;
if (a == 1)
goto out;
err=0;
out:
return err;
}
int cccc(int a)
{
int err=0;
if (a == 1) {
err = -5;
goto out;
}
out:
return err;
}
With gcc 3.2.2 for x86, both constructs generated the same code:
pushl %ebp
movl %esp, %ebp
xorl %eax, %eax
cmpl $1, 8(%ebp)
setne %al
leal -5(%eax,%eax,4), %eax
leave
ret
With gcc 2.96 (Mandrake) however, the standard construct generated this:
pushl %ebp
movl %esp, %ebp
subl $4, %esp
movl $-5, -4(%ebp)
cmpl $1, 8(%ebp)
jne .L3
jmp .L4
.p2align 4,,7
.L3:
movl $0, -4(%ebp)
.L4:
movl -4(%ebp), %eax
movl %eax, %eax
movl %ebp, %esp
popl %ebp
ret
While moving the err setting into the conditional generates the following:
pushl %ebp
movl %esp, %ebp
subl $4, %esp
movl $0, -4(%ebp)
cmpl $1, 8(%ebp)
jne .L6
movl $-5, -4(%ebp)
jmp .L7
.p2align 4,,7
.L6:
nop
.L7:
movl -4(%ebp), %eax
movl %eax, %eax
movl %ebp, %esp
popl %ebp
ret
For PPC, gcc 3.3.3, the standard construct gave:
xori 3,3,1
addic 3,3,-1
subfe 3,3,3
rlwinm 3,3,0,30,28
blr
While moving the err setting into the conditional generates the following:
xori 3,3,1
srawi 0,3,31
xor 3,0,3
subf 3,3,0
srawi 3,3,31
andi. 3,3,5
addi 3,3,-5
blr
So, it looks like the standard construct can actually generate better code in
some cases, its almost never worse, and it's certainly nicer to read.
Chris
next prev parent reply other threads:[~2004-11-03 16:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-02 20:08 question on common error-handling idiom Chris Friesen
2004-11-02 20:58 ` Jan Engelhardt
2004-11-02 21:12 ` linux-os
2004-11-03 10:45 ` Ross Kendall Axe
2004-11-02 21:12 ` Russell Miller
2004-11-02 21:16 ` Jesper Juhl
2004-11-02 21:21 ` Oliver Neukum
2004-11-02 21:29 ` Jan Engelhardt
2004-11-02 21:48 ` Jesper Juhl
2004-11-03 16:49 ` Chris Friesen [this message]
2004-11-03 8:11 ` GNicz
2004-11-04 19:52 ` Linus Torvalds
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=41890C0F.6080702@nortelnetworks.com \
--to=cfriesen@nortelnetworks.com \
--cc=jengelh@linux01.gwdg.de \
--cc=juhl-lkml@dif.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=oliver@neukum.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