Date: Tue, 15 Jul 1997 16:59:48 +0200 From: Christoph Kukulies <kuku@gilberto.physik.rwth-aachen.de> To: "M. L. Dodson" <bdodson@beowulf.utmb.edu> Cc: freebsd-questions@freefall.FreeBSD.org, kuku@gilberto.physik.rwth-aachen.de Subject: Re: should I report a cc1 internal compiler error? Message-ID: <19970715165948.08825@gil.physik.rwth-aachen.de> In-Reply-To: <199707151403.JAA08521@beowulf.utmb.edu>; from "M. L. Dodson" <bdodson@beowulf.utmb.edu> on Tue, Jul 15, 1997 at 09:03:44AM -0500 References: <199707151403.JAA08521@beowulf.utmb.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jul 15, 1997 at 09:03:44AM -0500, M. L. Dodson wrote:
>
> Maybe, but first make sure you haven't gotten a pointer pointing
> wildly out of range in your assembly code. You might try including
It's during compilation cc -c file.c, not a run time sig11 of the program.
> the code fragment causing the sig11 in a post.
It's (sure a bad example of programming practice) the following code
snippet which emerged after modifying an example (a question) posted
in another maillist.
multiply(char c)
{
short int r;
asm volatile ("
movb $2,%%eax
imulb %0
movw %%eax,%1"
: "=1" (r)
: "0" (c) : "eax" );
return r;
}
The crucial point is the char c in the parameter list causing
the FreeBSD cc1 to sig11.
>
> Please note that this question might be better targeted to a C/Assembler
> mailing list/newsgroup.
>
> Bud Dodson
>
> >
> >
> > While experimenting with some inline asm statements
> > I caused an internal compiler error:
> >
> > cc: Internal compiler error: program cc1 got fatal signal 11
> >
> > Should I report this to the gnu-cc list?
> >
> > --
> > Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de
> >
>
> --
> M. L. Dodson bdodson@scms.utmb.edu
> 409-772-2178 FAX: 409-772-1790
--
Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19970715165948.08825>