g++ sucks: internal compiler error???

[Pete]

Re: g++ sucks: internal compiler error???

Jonathan Turkanis wrote:
<snip>[color=blue]
> VC6, on the other hand, gives me ICEs all the time with
> perfectly correct code, even when I use the standard workarounds.[/color]

Why do you expect VC6 to work with code written to the C++ standard, when it
was released before the standard was?
Yes, VC7.0 is inexcusable, but VC7.1 made up for it nicely.

- Pete

[Rolf Magnus]

Re: g++ sucks: internal compiler error???

Claudio Puviani wrote:
[color=blue]
> "Jonathan Turkanis" <technews@kanga roologic.com> wrote[color=green]
>> I've never had an ICE on GCC that didn't represent a problem with my
>> code. VC6, on the other hand, gives me ICEs all the time with
>> perfectly correct code, even when I use the standard workarounds.[/color]
>
> I'd be careful making up abbreviations. An ICE is an in-circuit
> emulator, not an internal compiler error. :-)[/color]

I was thinking of a german high speed train ;-)

[Jonathan Turkanis]

Re: g++ sucks: internal compiler error???


"Claudio Puviani" <puviani@hotmai l.com> wrote in message
news:a3hbc.2473 7$Nu3.6619071@n ews4.srv.hcvlny .cv.net...[color=blue]
> "Jonathan Turkanis" <technews@kanga roologic.com> wrote[color=green]
> > I've never had an ICE on GCC that didn't represent a problem with[/color][/color]
my[color=blue][color=green]
> > code. VC6, on the other hand, gives me ICEs all the time with
> > perfectly correct code, even when I use the standard workarounds.[/color]
>
> I'd be careful making up abbreviations. An ICE is an in-circuit[/color]
emulator,[color=blue]
> not an internal compiler error. :-)
>[/color]

Also an integral constant expression. I think its clear from context
;-)

Jonathan

[Jonathan Turkanis]

Re: g++ sucks: internal compiler error???


"Pete" <x@x.x> wrote in message
news:rgibc.1269 6$lt2.10045@new sread1.news.pas .earthlink.net. ..[color=blue]
> Jonathan Turkanis wrote:
> <snip>[color=green]
> > VC6, on the other hand, gives me ICEs all the time with
> > perfectly correct code, even when I use the standard workarounds.[/color]
>
> Why do you expect VC6 to work with code written to the C++ standard,[/color]
when it[color=blue]
> was released before the standard was?[/color]

I don't. But with a little work i can usually make it work.
[color=blue]
> Yes, VC7.0 is inexcusable, but VC7.1 made up for it nicely.[/color]

VC7.1 is my main compiler. But I like my code to work, whenever
possible, on a number of others, including a couple of antique ones
like Borland 5.x and VC6.

Jonathan

[Jonathan Turkanis]

Re: g++ sucks: internal compiler error???


"Claudio Puviani" <puviani@hotmai l.com> wrote in message
news:a3hbc.2473 7$Nu3.6619071@n ews4.srv.hcvlny .cv.net...[color=blue]
> "Jonathan Turkanis" <technews@kanga roologic.com> wrote[color=green]
> > I've never had an ICE on GCC that didn't represent a problem with[/color][/color]
my[color=blue][color=green]
> > code. VC6, on the other hand, gives me ICEs all the time with
> > perfectly correct code, even when I use the standard workarounds.[/color]
>
> I'd be careful making up abbreviations. An ICE is an in-circuit[/color]
emulator,[color=blue]
> not an internal compiler error. :-)[/color]

I just read your post again. I didn't make up ICE -- it's an accepted
abbreviation. See, e.g.,

http://lists.boost.org/MailArchives/boost/msg50047.php

Jonathan

[Claudio Puviani]

Re: g++ sucks: internal compiler error???

"Jonathan Turkanis" <technews@kanga roologic.com> wrote[color=blue]
>
> I just read your post again. I didn't make up ICE -- it's an
> accepted abbreviation. See, e.g.,
> http://lists.boost.org/MailArchives/boost/msg50047.php[/color]

Um... well, you're just showing me another usenet posting. On usenet
postings, I've seen things like "axe" instead "ask", "your" instead or
"you're" (and vice versa), people calling VAX systems "supercomputers " or
"mainframes " and the list goes on.

As far as computer dictionaries and long-standing common practice go, "ICE"
just doesn't mean "internal compiler error".

But it was clear from the context what you meant, once I reread the sentence
not mentally substituting "in-circuit emulator". :-)

Claudio Puviani

[Jonathan Turkanis]

Re: g++ sucks: internal compiler error???


"Claudio Puviani" <puviani@hotmai l.com> wrote in message
news:Lcnbc.2714 7$Nu3.7815392@n ews4.srv.hcvlny .cv.net...[color=blue]
> "Jonathan Turkanis" <technews@kanga roologic.com> wrote[color=green]
> >
> > I just read your post again. I didn't make up ICE -- it's an
> > accepted abbreviation. See, e.g.,
> > http://lists.boost.org/MailArchives/boost/msg50047.php[/color]
>
> Um... well, you're just showing me another usenet posting. On usenet
> postings, I've seen things like "axe" instead "ask", "your" instead[/color]
or[color=blue]
> "you're" (and vice versa), people calling VAX systems[/color]
"supercomputers " or[color=blue]
> "mainframes " and the list goes on.[/color]

I don't want to get into an argument here.

I was giving an example to show that 'internal compiler error' is
*one* establied meaning of ICE. You can find lots more on Google:

http://www.google.com/search?q=ICE+%22internal+compiler+error%22

Lots of abbreviations have more than one meaning. E.g., PA means
'Peano Arithmetic' to logicians, 'Propositional Attitudes' to
philosophers and 'Pennsylvania' to the US Postal Service.

In my circles, ICE means 'internal compiler error', 'intergral
constant expression' and -- I almost forgot -- 'frozen water'.

Jonathan

[Frederic Banaszak]

Re: g++ sucks: internal compiler error???


Just so you stop this ridiculous and petty thread, look here

http://www.geocities.com/ikind_babel/babel/babel.html#I

See, you're both right. Happy now?


I didn't think so.


Carry on.

[Jonathan Turkanis]

Re: g++ sucks: internal compiler error???


"Frederic Banaszak" <banaszak@hotma il.com> wrote in message
news:qlas601t1m a6o3nauk8d4mjbv 3h5ub7vv4@4ax.c om...
[color=blue]
> Just so you stop this ridiculous and petty thread,[/color]

Come on -- I was having fun!
[color=blue]
> look here
> http://www.geocities.com/ikind_babel/babel/babel.html#I[/color]

Thanks. Now I can say 'ICE' without feeling like I'm speaking some
strange hillbilly dialect.

Jonathan

[Alf P. Steinbach]

Re: g++ sucks: internal compiler error???

<off-topic>

* "Claudio Puviani" <puviani@hotmai l.com> schriebt:[color=blue]
>
> As far as computer dictionaries and long-standing common practice go, "ICE"
> just doesn't mean "internal compiler error".[/color]

I don't know about the dictionaries but practice is that for programmers
"ICE" does mean "internal compiler error". Also the expression "the compiler
iced" means it crashed or reported an internal error. The g++ compiler team
generally reacts very fast to ICEs, which they provide an effortless way of
reporting; Microsoft, on the other hand, goes out of its way (with dis-info
and such) to make it near to impossible to figure out how to report ICEs, or
in general to report errors with any of their products except auto crash info.

</off-topic>

--
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?

[Neil Zanella]

Re: g++ sucks: internal compiler error???

"Jonathan Turkanis" <technews@kanga roologic.com> wrote in message
[color=blue]
> I guess I wasn't very clear. I was just trying to make what I thought
> was an obvious point, but might not be to someone who has never seen
> an internal compiler error: the internal error, which is clearly a
> problem with the compiler, usually goes away when an error is
> corrected. The error can often be spotted by using a second or third
> compiler. If the code turns out to be correct, there is usually a way
> to rewrite the code so that the compiler will accept it.
>
> I've never had an ICE on GCC that didn't represent a problem with my
> code. VC6, on the other hand, gives me ICEs all the time with
> perfectly correct code, even when I use the standard workarounds.
>
> Jonathan[/color]

Well, I happened to recompile the code with the same compiler from
Red Hat 9 (and I am running on Fedora Core 1). Nevertheless, the
Red Hat 9 version appears to have some patches in its versioning
string. And on that computer, the code compiles fine. Now, I was
not able to reproduce the error in a smaller example (which,
when doing what appears to be exactly the same thing, does
not crash). I would love to share this compiler bug with
you all, but do you really want me to post 1000 lines of
code simply because I cannot reproduce a smaller file
that produces the same error???

I'm not sure that would be acceptable. When the errors
are not internal, usually, I am able to reproduce them
in smaller code snippets.

Thanks,

Neil

[Jonathan Turkanis]

Re: g++ sucks: internal compiler error???


"Neil Zanella" <nzanella@cs.mu n.ca> wrote in message
news:b68d2f19.0 404022012.73106 977@posting.goo gle.com...[color=blue]
> "Jonathan Turkanis" <technews@kanga roologic.com> wrote in message
>[/color]
[color=blue]
> Well, I happened to recompile the code with the same compiler from
> Red Hat 9 (and I am running on Fedora Core 1). Nevertheless, the
> Red Hat 9 version appears to have some patches in its versioning
> string. And on that computer, the code compiles fine.[/color]

Unfortunately, that's not surprising. Very frustrating, though. I
know it may not be possible in your case, but it might be helpful to
try it on a completely different compiler. Intel, maybe?
[color=blue]
> Now, I was
> not able to reproduce the error in a smaller example (which,
> when doing what appears to be exactly the same thing, does
> not crash). I would love to share this compiler bug with
> you all, but do you really want me to post 1000 lines of
> code simply because I cannot reproduce a smaller file
> that produces the same error???[/color]

I know the feeling. I think I said somewhere in this thread that I've
never had an internal error in g++ that didn't turn out to reflect an
error in my code; with VC6 I often get internal errors from code which
use techniques which I know work in isolation -- putting them all
together causes the ICE. Often there is a large amount of code
involved.

It's a painful process, but I can usually find out what's casuing the
ICE by including headers one at a time. When I find the first header
that causes the error (and verify that none of its includes are
causing the problem) I comment everything out, then uncomment it
systematically until the error resurfaces. Often the error can be
corrected by replacing a small bit of code with code which has exactly
the same meaning but is phrased slightly differently. Occasionally it
has required a substantial redesign. Very rarely I have been unable to
get the compiler to accept any code which does what I want and have
had to abandon my plans.
[color=blue]
> I'm not sure that would be acceptable. When the errors
> are not internal, usually, I am able to reproduce them
> in smaller code snippets.[/color]

I'd say it's probably against newsgroup policy to post so much code,
but if it's really only 1000 lines, I can't think of anywhere better
than here. I'll look at; but I probably don't have the time or stamina
to track down the error. Someone else might -- perhaps someone who's
had the same problem in the past.

Sorry this thread got so far off track.

Jonathan

[Joe]

Re: g++ sucks: internal compiler error???

use VC++, gnu is crap

"Neil Zanella" <nzanella@cs.mu n.ca> wrote in message
news:b68d2f19.0 404012249.2f08f 7df@posting.goo gle.com...[color=blue]
> Hello,
>
> Allow me to share my frustrations with GNU g++. This is the second
> time something similar happens to me: I can't find anything wrong with
> my C++ program and yet I get segfaults, and eventually, here is what
> happens. Anyone ever experience anything similar. This or similar
> untrackable problems happen to me whenever I write a large class...
> anyone have had similar experiences???
>
> make
> g++ -c matrix.cpp -Wall -g
> matrix.cpp: In member function `void
> Matrix::compute DistShortest(bo ol)':
> matrix.cpp:189: internal compiler error: in find_function_d ata, at
> function.c:
> 313
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See <URL:http://bugzilla.redhat .com/bugzilla> for instructions.
> Preprocessed source stored into /tmp/ccf7vSby.out file, please attach
> this to your bugreport
> make: *** [matrix.o] Error 1[/color]

[Steven T. Hatton]

Re: g++ sucks: internal compiler error???

Jonathan Turkanis wrote:
[color=blue]
> I know the feeling. I think I said somewhere in this thread that I've
> never had an internal error in g++ that didn't turn out to reflect an
> error in my code;[/color]

I have been using GCC for the past 7 years on a daily basis to compile my
own, and other people's code. I cannot count the number of problems I have
had due to a flaw in GCC, because counting begins with 1, and I thus have
no place to begin.

--
p->m == (*p).m == p[0].m

http://www.kdevelop.org

http://www.suse.com

http://www.mozilla.org

[Jorge Rivera]

Re: g++ sucks: internal compiler error???

> I would love to share this compiler bug with[color=blue]
> you all, but do you really want me to post 1000 lines of
> code simply because I cannot reproduce a smaller file
> that produces the same error???
>[/color]

Then I have to ask. Why did you post? Talk to somebody at work, home
or a bar...
[color=blue]
> I'm not sure that would be acceptable.[/color]

No it wouldn't be nice (I don't think it would be much worse than this
response, though :) ).

JLR