public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "d.g.gorbachev at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/56167] New: ICE with invalid __attribute__ arguments
Date: Fri, 01 Feb 2013 01:50:00 -0000	[thread overview]
Message-ID: <bug-56167-4@http.gcc.gnu.org/bugzilla/> (raw)


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56167

             Bug #: 56167
           Summary: ICE with invalid __attribute__ arguments
    Classification: Unclassified
           Product: gcc
           Version: 4.8.0
            Status: UNCONFIRMED
          Severity: minor
          Priority: P3
         Component: middle-end
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: d.g.gorbachev@gmail.com


$ cat > bug.c
extern void foo(void) __attribute__((target(0)));

int main(void)
{
  foo();
  return 0;
}
^D
$ gcc -S bug.c
bug.c:1:1: internal compiler error: in ix86_valid_target_attribute_inner_p, at
config/i386/i386.c:4226
 extern void foo(void) __attribute__((target(0)));
 ^
[...]
$ sed -i s/target/error/ bug.c
$ gcc -S bug.c
bug.c: In function 'main':
bug.c:5:6: internal compiler error: tree check: expected string_cst, have
integer_cst in expand_expr_real_1, at expr.c:10191
   foo();
      ^
[...]
$ sed -i s/error/warning/ bug.c
$ gcc -S bug.c
bug.c: In function 'main':
bug.c:5:6: internal compiler error: tree check: expected string_cst, have
integer_cst in expand_expr_real_1, at expr.c:10198
   foo();
      ^
[...]

A few other __attribute__ bugs:

$ sed -i s/warning/weakref/ bug.c
$ gcc -S bug.c
bug.c:1:1: error: attribute 'alias' argument not a string
 extern void foo(void) __attribute__((weakref(0)));
 ^
bug.c:1:13: warning: 'weakref' attribute should be accompanied with an 'alias'
attribute [-Wattributes]
 extern void foo(void) __attribute__((weakref(0)));
             ^
$ sed -i s/weakref/section/ bug.c
$ gcc -S bug.c
bug.c:1:13: error: section attribute not allowed for 'foo'
 extern void foo(void) __attribute__((section(0)));
             ^
$ echo 'void *foo(int) __attribute__((alloc_size("1")));' > 1.c
$ gcc -S 1.c
1.c:1:1: warning: alloc_size parameter outside range [-Wattributes]
 void *foo(int) __attribute__((alloc_size("1")));
 ^


             reply	other threads:[~2013-02-01  1:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-01  1:50 d.g.gorbachev at gmail dot com [this message]
2013-02-01  7:43 ` [Bug middle-end/56167] " jakub at gcc dot gnu.org
2013-02-01  7:52 ` jakub at gcc dot gnu.org
2013-02-01  7:55 ` jakub at gcc dot gnu.org
2013-02-01 16:22 ` d.g.gorbachev at gmail dot com
2013-02-05  8:08 ` jakub at gcc dot gnu.org
2013-02-05  8:11 ` 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-56167-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: 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).