From: "Todd Goodman" <tsg1@earthlink.net>
To: <cygwin@sourceware.cygnus.com>
Subject: GCC Internal Compiler Error When Compiling with -pipe
Date: Sun, 28 Feb 1999 08:14:00 -0000 [thread overview]
Message-ID: <000b01be6334$c2405dc0$0301a8c0@tgoodman8> (raw)
Back in November there was a brief discussion of the error:
Making all in common
gcc -DHAVE_CONFIG_H -I. -I. -I.. -g -O2 -Wall -pipe -c capability.c
/home/noer/src/b20/comp-tools/devo/gcc/pexecute.c:245: Internal compiler
error in function pexecute
Mumit asked if it went away when building without -pipe and it does indeed.
Would it be useful if I put up the code that produces this problem on a web
site
(it's from Freeciv)?
Is there any update on this or should I plan to look into it?
Thanks,
Todd
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
WARNING: multiple messages have this Message-ID
From: "Todd Goodman" <tsg1@earthlink.net>
To: <cygwin@sourceware.cygnus.com>
Subject: GCC Internal Compiler Error When Compiling with -pipe
Date: Sun, 28 Feb 1999 23:02:00 -0000 [thread overview]
Message-ID: <000b01be6334$c2405dc0$0301a8c0@tgoodman8> (raw)
Message-ID: <19990228230200.8Jz0IM4hAwPMKQ48YTCVCtBvoFUtZ-N3TVntuELtIYs@z> (raw)
Back in November there was a brief discussion of the error:
Making all in common
gcc -DHAVE_CONFIG_H -I. -I. -I.. -g -O2 -Wall -pipe -c capability.c
/home/noer/src/b20/comp-tools/devo/gcc/pexecute.c:245: Internal compiler
error in function pexecute
Mumit asked if it went away when building without -pipe and it does indeed.
Would it be useful if I put up the code that produces this problem on a web
site
(it's from Freeciv)?
Is there any update on this or should I plan to look into it?
Thanks,
Todd
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next reply other threads:[~1999-02-28 8:14 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-28 8:14 Todd Goodman [this message]
[not found] ` < 000b01be6334$c2405dc0$0301a8c0@tgoodman8 >
1999-02-28 8:41 ` Mumit Khan
1999-02-28 23:02 ` Mumit Khan
1999-02-28 23:02 ` Todd Goodman
1999-02-28 16:04 N8TM
[not found] ` < 2877cf50.36d9d908@aol.com >
1999-02-28 20:37 ` Mumit Khan
1999-02-28 23:02 ` Mumit Khan
1999-03-03 8:10 ` Chris Faylor
[not found] ` < 19990302221235.C3492@cygnus.com >
1999-03-03 10:28 ` Todd Goodman
1999-03-31 19:45 ` Todd Goodman
1999-03-31 19:45 ` Chris Faylor
1999-02-28 23:02 ` N8TM
1999-03-03 8:31 Suhaib M. Siddiqi
[not found] ` < 001101be6595$72ce0770$29acdfd0@InspirePharm.Com >
1999-03-03 15:58 ` Chris Faylor
1999-03-31 19:45 ` Chris Faylor
1999-03-31 19:45 ` Suhaib M. Siddiqi
1999-03-03 10:36 Suhaib M. Siddiqi
[not found] ` < 007e01be65a6$e3f98670$29acdfd0@InspirePharm.Com >
1999-03-03 19:06 ` Todd Goodman
1999-03-31 19:45 ` Todd Goodman
1999-03-31 19:45 ` Suhaib M. Siddiqi
1999-03-03 16:57 Suhaib M. Siddiqi
1999-03-31 19:45 ` Suhaib M. Siddiqi
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='000b01be6334$c2405dc0$0301a8c0@tgoodman8' \
--to=tsg1@earthlink.net \
--cc=cygwin@sourceware.cygnus.com \
/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).