public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "trippels at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/59644] [4.9 Regression] r206243 miscompiles Linux kernel
Date: Tue, 31 Dec 2013 13:03:00 -0000 [thread overview]
Message-ID: <bug-59644-4-7pYfVBIGRm@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59644-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59644
--- Comment #8 from Markus Trippelsdorf <trippels at gcc dot gnu.org> ---
>From the printk.i:
38333 int printk_emit(int facility, int level,
38334 const char *dict, size_t dictlen,
38335 const char *fmt, ...)
38336 {
38337 va_list args;
38338 int r;
38339
38340 __builtin_va_start(args,fmt);
38341 r = vprintk_emit(facility, level, dict, dictlen, fmt, args);
38342 __builtin_va_end(args);
38343
38344 return r;
38345 }
38346 ;
38347 # 1676 "kernel/printk/printk.c"
38348 int printk(const char *fmt, ...)
38349 {
38350 va_list args;
38351 int r;
38352 # 1689 "kernel/printk/printk.c"
38353 __builtin_va_start(args,fmt);
38354 r = vprintk_emit(0, -1, ((void *)0), 0, fmt, args);
38355 __builtin_va_end(args);
38356
38357 return r;
38358 }
38359 ;
dump_stack_set_arch_desc is also a call wrapped by __builtin_va_start
__builtin_va_end.
next prev parent reply other threads:[~2013-12-31 13:03 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-30 23:03 [Bug tree-optimization/59644] New: " trippels at gcc dot gnu.org
2013-12-30 23:43 ` [Bug tree-optimization/59644] " jakub at gcc dot gnu.org
2013-12-31 8:17 ` trippels at gcc dot gnu.org
2013-12-31 8:18 ` trippels at gcc dot gnu.org
2013-12-31 8:19 ` trippels at gcc dot gnu.org
2013-12-31 8:20 ` trippels at gcc dot gnu.org
2013-12-31 8:26 ` trippels at gcc dot gnu.org
2013-12-31 11:47 ` jakub at gcc dot gnu.org
2013-12-31 13:03 ` trippels at gcc dot gnu.org [this message]
2014-01-06 8:21 ` trippels at gcc dot gnu.org
2014-01-06 8:48 ` trippels at gcc dot gnu.org
2014-01-06 9:08 ` jakub at gcc dot gnu.org
2014-01-06 9:17 ` trippels at gcc dot gnu.org
2014-01-06 9:26 ` jakub at gcc dot gnu.org
2014-01-06 9:36 ` trippels at gcc dot gnu.org
2014-01-06 10:00 ` trippels at gcc dot gnu.org
2014-01-06 10:04 ` trippels at gcc dot gnu.org
2014-01-06 10:09 ` hjl.tools at gmail dot com
2014-01-06 10:12 ` jakub at gcc dot gnu.org
2014-01-06 10:21 ` trippels at gcc dot gnu.org
2014-01-06 11:28 ` jakub at gcc dot gnu.org
2014-01-06 11:55 ` jakub at gcc dot gnu.org
2014-01-06 13:39 ` [Bug target/59644] " jakub at gcc dot gnu.org
2014-01-06 21:38 ` jakub at gcc dot gnu.org
2014-01-06 21:39 ` jakub at gcc dot gnu.org
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=bug-59644-4-7pYfVBIGRm@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).