diff options
author | upstream source tree <ports@midipix.org> | 2015-03-15 20:14:05 -0400 |
---|---|---|
committer | upstream source tree <ports@midipix.org> | 2015-03-15 20:14:05 -0400 |
commit | 554fd8c5195424bdbcabf5de30fdc183aba391bd (patch) | |
tree | 976dc5ab7fddf506dadce60ae936f43f58787092 /gcc/testsuite/gcc.dg/20051207-3.c | |
download | cbb-gcc-4.6.4-554fd8c5195424bdbcabf5de30fdc183aba391bd.tar.bz2 cbb-gcc-4.6.4-554fd8c5195424bdbcabf5de30fdc183aba391bd.tar.xz |
obtained gcc-4.6.4.tar.bz2 from upstream website;upstream
verified gcc-4.6.4.tar.bz2.sig;
imported gcc-4.6.4 source tree from verified upstream tarball.
downloading a git-generated archive based on the 'upstream' tag
should provide you with a source tree that is binary identical
to the one extracted from the above tarball.
if you have obtained the source via the command 'git clone',
however, do note that line-endings of files in your working
directory might differ from line-endings of the respective
files in the upstream repository.
Diffstat (limited to 'gcc/testsuite/gcc.dg/20051207-3.c')
-rw-r--r-- | gcc/testsuite/gcc.dg/20051207-3.c | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/gcc/testsuite/gcc.dg/20051207-3.c b/gcc/testsuite/gcc.dg/20051207-3.c new file mode 100644 index 000000000..3d4b2a48c --- /dev/null +++ b/gcc/testsuite/gcc.dg/20051207-3.c @@ -0,0 +1,7 @@ +/* GCC doesn't generate any .eh_frame data for this TU itself, so it + shouldn't warn about "a" conflicting with the built-in idea of + .eh_frame. The warning therefore belongs on the second decl. */ +/* { dg-options "-fno-unit-at-a-time" } */ +/* { dg-require-named-sections "" } */ +int a __attribute__((section (".eh_frame"))) = 1; +const int b __attribute__((section (".eh_frame"))) = 1; /* { dg-error "section type conflict" } */ |