completely
Product: gcc
Version: 4.3.2
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: esigra at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi
--- Comment #2 from esigra at gmail dot com 2009-01-30 16:12 ---
GCC already understands the semantics of strlen. If one of the operands to
is a constant and the other is strlen, it is optimized (such as strlen(str) =
1). It just seems like the case with strlen on both sides is missing
Version: 4.3.3
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: esigra at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40614
Component: ada
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: esigra at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37618
--- Comment #1 from esigra at gmail dot com 2008-09-23 09:38 ---
Created an attachment (id=16383)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=16383action=view)
Makefile
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37618
: declaration of
Finalize hides one at line N
Product: gcc
Version: 4.2.3
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: ada
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: esigra at gmail
--- Comment #1 from esigra at gmail dot com 2008-09-23 09:51 ---
Created an attachment (id=16386)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=16386action=view)
Makefile
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37619
--- Comment #2 from esigra at gmail dot com 2008-09-23 09:51 ---
Created an attachment (id=16387)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=16387action=view)
specification
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37619
--- Comment #3 from esigra at gmail dot com 2008-09-23 09:52 ---
Created an attachment (id=16388)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=16388action=view)
implementation
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37619
--- Comment #2 from esigra at gmail dot com 2008-09-23 09:39 ---
Created an attachment (id=16384)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=16384action=view)
specification
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37618
--- Comment #3 from esigra at gmail dot com 2008-09-23 09:39 ---
Created an attachment (id=16385)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=16385action=view)
implementation
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37618
--- Comment #1 from esigra at gmail dot com 2008-09-23 10:26 ---
Created an attachment (id=16390)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=16390action=view)
Makefile
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37620
--- Comment #2 from esigra at gmail dot com 2008-09-23 10:27 ---
Created an attachment (id=16391)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=16391action=view)
implementation
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37620
Priority: P3
Component: ada
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: esigra at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37620
--- Comment #3 from esigra at gmail dot com 2008-09-23 10:32 ---
Created an attachment (id=16392)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=16392action=view)
Makefile
--
esigra at gmail dot com changed:
What|Removed |Added
--- Comment #6 from esigra at gmail dot com 2008-10-05 13:42 ---
This problem went away for me when I upgraded to GCC 4.3.1 (Gentoo x86), so it
seems to be fixed.
--
esigra at gmail dot com changed:
What|Removed |Added
--- Comment #2 from esigra at gmail dot com 2008-05-06 17:27 ---
I would definitely like GCC to produce colourized output. It can really improve
the readability. I miss that feature. It has my vote.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36150
--- Comment #4 from esigra at gmail dot com 2008-05-06 18:00 ---
(In reply to comment #3)
2) Standards are not freely distributable, thus they are not widely available.
You say that as if it was a general fact, but it is certainly not. For example
the Ada reference manual is available
--- Comment #6 from esigra at gmail dot com 2008-05-06 18:40 ---
(In reply to comment #4)
I rather not add too much complexity to gcc diagnostic output. Which means
no color.
We did not demand that you do it personally. We just think that it would be a
really good idea if someone
--- Comment #6 from esigra at gmail dot com 2008-05-06 18:47 ---
(In reply to comment #5)
But seriously colorization should not be done in the compiler. Just like IDE
should not be part of the compiler ...
Colorization of a message is part of the message. It should obviously be done
--- Comment #8 from esigra at gmail dot com 2008-05-06 21:55 ---
(In reply to comment #7)
If you added escape sequences to the string constants in the gcc source
then it would only work for the C locale messages.
Adding escape sequences for colours would work as well
--- Comment #8 from esigra at gmail dot com 2008-05-07 13:08 ---
(In reply to comment #7)
Adding color output (ala ls --color) or the proposal in this bug (gcc as a
lecturer in programming) show a critical misunderstanding: Assuming that GCC
developers are bored and have nothing
--- Comment #11 from esigra at gmail dot com 2008-09-21 20:38 ---
I found that James' wish is already implemented in some cases:
$ strings /usr/i686-pc-linux-gnu/gnat-gcc-bin/4.2/gnat|grep RM
illegal use of remote access-to-class-wide type, see RM E.4(18)
A user that gets that error
23 matches
Mail list logo
