public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "danglin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/65818] New: libiberty/vprintf-support.c:41:1: ICE: in expand_i fn_va_arg_1, at tree-stdarg.c:1095 Date: Mon, 20 Apr 2015 20:44:00 -0000 [thread overview] Message-ID: <bug-65818-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65818 Bug ID: 65818 Summary: libiberty/vprintf-support.c:41:1: ICE: in expand_i fn_va_arg_1, at tree-stdarg.c:1095 Product: gcc Version: 6.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: danglin at gcc dot gnu.org Host: hppa2.0w-hp-hpux11.11 Target: hppa2.0w-hp-hpux11.11 Build: hppa2.0w-hp-hpux11.11 if [ x"-fPIC" != x ]; then \ /test/gnu/gcc/objdir/./prev-gcc/xgcc -B/test/gnu/gcc/objdir/./prev-gcc / -B/opt/gnu/gcc/gcc-6.0/hppa2.0w-hp-hpux11.11/bin/ -B/opt/gnu/gcc/gcc-6.0/hppa2 .0w-hp-hpux11.11/bin/ -B/opt/gnu/gcc/gcc-6.0/hppa2.0w-hp-hpux11.11/lib/ -isystem /opt/gnu/gcc/gcc-6.0/hppa2.0w-hp-hpux11.11/include -isystem /opt/gnu/gcc/gcc-6. 0/hppa2.0w-hp-hpux11.11/sys-include -c -DHAVE_CONFIG_H -g -O2 -I. -I../../gc c/libiberty/../include -W -Wall -Wwrite-strings -Wc++-compat -Wstrict-prototype s -pedantic -fPIC ../../gcc/libiberty/vprintf-support.c -o pic/vprintf-support. o; \ else true; fi ../../gcc/libiberty/vprintf-support.c: In function 'libiberty_vprintf_buffer_siz e': ../../gcc/libiberty/vprintf-support.c:41:1: internal compiler error: in expand_i fn_va_arg_1, at tree-stdarg.c:1095 libiberty_vprintf_buffer_size (const char *format, va_list args) ^
next reply other threads:[~2015-04-20 20:44 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-04-20 20:44 danglin at gcc dot gnu.org [this message] 2015-04-20 20:49 ` [Bug tree-optimization/65818] " danglin at gcc dot gnu.org 2015-04-21 7:45 ` [Bug tree-optimization/65818] [6 Regression] " rguenth at gcc dot gnu.org 2015-04-21 18:50 ` vries at gcc dot gnu.org 2015-04-22 6:44 ` vries at gcc dot gnu.org 2015-04-22 7:02 ` vries at gcc dot gnu.org 2015-04-22 7:15 ` vries at gcc dot gnu.org 2015-04-22 11:25 ` dave.anglin at bell dot net 2015-04-22 16:40 ` vries at gcc dot gnu.org 2015-04-22 16:58 ` dave.anglin at bell dot net 2015-04-24 11:21 ` dave.anglin at bell dot net 2015-04-24 16:40 ` vries at gcc dot gnu.org 2015-04-24 20:30 ` vries at gcc dot gnu.org 2015-04-25 12:36 ` vries at gcc dot gnu.org 2015-04-26 11:13 ` vries at gcc dot gnu.org 2015-04-28 6:05 ` vries at gcc dot gnu.org 2015-04-28 6:10 ` vries 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-65818-4@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: linkBe 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).