From: Chuck Ebbert <cebbert.lkml@gmail.com>
To: Jeff Epler <jepler@unpythonic.net>
Cc: "H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86: Clean up stack access code in irq_32.c
Date: Sun, 12 Oct 2014 12:40:13 -0500 [thread overview]
Message-ID: <20141012124013.41ea7473@as> (raw)
In-Reply-To: <20141012170003.GA96036@unpythonic.net>
On Sun, 12 Oct 2014 12:00:03 -0500
Jeff Epler <jepler@unpythonic.net> wrote:
> It looks like the proposed variant still miscompiles in clang 3.4 and 3.5, the
> two versions I had handy to test.
>
> I extracted your code to a simple standalone C translation unit and
> inspected various compilers' results via objdump.
>
Wow, my little test program below worked with clang by accident. I was
building it with both printf() calls enabled and it printed out the
same results on both output lines. But commenting out the first line
reveals that it simply leaves whatever junk is on the stack there
for the first arg when it calls printf().
#define _GNU_SOURCE
#include <string.h>
#include <stdio.h>
#include <unistd.h>
#define current_stack_pointer ({ \
unsigned long sp; \
asm("mov %%esp,%0" : "=g" (sp)); \
sp; \
})
#define current_stack_pointer2 ({ \
register unsigned long sp asm("esp"); \
sp; \
})
int main(int argc, char **argv)
{
// printf("%X %X\n", current_stack_pointer , __builtin_frame_address(0));
printf("%X %X\n", current_stack_pointer2, __builtin_frame_address(0));
return 0;
}
next prev parent reply other threads:[~2014-10-12 17:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-12 16:43 [PATCH] x86: Clean up stack access code in irq_32.c Chuck Ebbert
2014-10-12 16:47 ` H. Peter Anvin
2014-10-12 16:53 ` Chuck Ebbert
2014-10-12 17:00 ` Jeff Epler
2014-10-12 17:40 ` Chuck Ebbert [this message]
2014-10-12 17:13 ` H. Peter Anvin
2014-10-12 19:34 ` Chuck Ebbert
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=20141012124013.41ea7473@as \
--to=cebbert.lkml@gmail.com \
--cc=hpa@zytor.com \
--cc=jepler@unpythonic.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@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