bug or just an invalid commanline ?

[Jonathan Wakely]

On 20 March 2016 at 18:54, Nicholas Mc Guire wrote:
>
> Hi !
>
>  during some compiler testing to determin the impact of individual flags
>  on the layout of binaries I扉e been doing brute force iterations over
>  flags and stubled accross the following "internal compiler error"
>
>  This happens with:
>   * gcc (Debian 4.7.2-5) 4.7.2 on Debian 7.6
>   * gcc (Debian 4.9.2-10) 4.9.2 on Debian 8.1
>
> hofrat@debian:~/Diversity/testing$ cat hello.c
> #include <stdio.h>
>
> int main(int argc, char **argv) {
>         printf("hello, world\n");
>         return 0;
> }
> hofrat@debian:~/Diversity/testing$ gcc -fshort-double hello.c -c -o hello.o
> <built-in>:0:0: internal compiler error: in layout_type, at stor-layout.c:2121
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See <file:///usr/share/doc/gcc-4.7/README.Bugs> for instructions.
> Preprocessed source stored into /tmp/ccbpCZZY.out file, please attach this to your bugreport.
>
>  checking http://gcc.gnu.org/bugs.html#known it did not seem that this
>  qualifies as one of the known FP Non-bugs.

That page only lists some very frequently reported issues (and
non-issues). You need to search bugzilla to see if it's known.

>  Should this be reported or is this just an absurd commanline here ?
>  (all other single flags pass - some with legitimate warnings)

All internal compiler errors are bugs, always. The compiler should
never crash on invalid input or invalid command lines, it should give
an error.