--- Comment #4 from manu at gcc dot gnu dot org 2008-03-10 00:52 ---
(In reply to comment #2)
>
> Actually, I like that response. I might try to use it myself next time one of
> our customers reports a problem.
I guess that your contracted GCC support developers may give you a reply t
--- Comment #3 from manu at gcc dot gnu dot org 2008-03-10 00:37 ---
@Adam,
If you think that something is wrong in the documentation, please point out
exactly which text should be removed and what should be added. Also, feel free
to submit a documentation patch: http://gcc.gnu.org/cont
--- Comment #2 from adam at irvine dot com 2008-03-07 00:08 ---
(In reply to comment #1)
> > but others are
> actual bugs in which the compiler is generating incorrect instructions
> (such as #12331);
>
> That is not incorrect instructions. Just different than what you are
> expecting.
--- Comment #1 from pinskia at gcc dot gnu dot org 2008-03-06 23:58 ---
> but others are
actual bugs in which the compiler is generating incorrect instructions
(such as #12331);
That is not incorrect instructions. Just different than what you are
expecting. All can be defected by the
4 matches
Mail list logo