https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116644
--- Comment #2 from Iru Cai ---
(In reply to Eric Botcazou from comment #1)
> Why is that insufficient exactly? 256 is clearly not in range of My_Byte.
I mean the warning messages don't have the information pointing out which code
in this line
y: P3
Component: ada
Assignee: unassigned at gcc dot gnu.org
Reporter: mytbk920423 at gmail dot com
CC: dkm at gcc dot gnu.org
Target Milestone: ---
When compiling the following Ada code, GCC gives a warning with the correct
line number, but doesn't have
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115824
--- Comment #11 from Iru Cai ---
(In reply to Sam James from comment #7)
> (In reply to Randy MacLeod from comment #5)
>
> As far as I know, the commit itself is fine, and it's the pesky middle-end
> warnings again getting confused.
>
> Jonath
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115824
--- Comment #6 from Iru Cai ---
I build a GCC with 12.3.0 source, and replace the libstdc++ with the 12.4.0
one, and reproduce this problem.
Severity: normal
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: mytbk920423 at gmail dot com
Target Milestone: ---
The following code has a strange warning on GCC 12.4.0 when compiled with -O2
-Warray-bounds
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: mytbk920423 at gmail dot com
Target Milestone: ---
For example, the following C++ code has three namespaces:
namespace test_ns
{
namespace test_ns_1
{
struct A_Record { int x, y; };
}
namespace test_ns_2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102909
--- Comment #3 from Iru Cai ---
Looks like this kind of things are detected in the front-end. The GNAT
front-end can warn on the similar things:
procedure Main is
A : Integer;
B : constant Integer := 1;
begin
A := 0;
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102909
--- Comment #2 from Iru Cai ---
So it looks something like https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44677
GCC thinks ``a`` is set but not used in ``a = 1 + b;``, but is used in ``a = 1;
a += b;``.
Assignee: unassigned at gcc dot gnu.org
Reporter: mytbk920423 at gmail dot com
Target Milestone: ---
GCC misses the -Wunused-but-set-variable in the some code (GCC and Clang output
can be seen in https://godbolt.org/z/7658M4qra).
I first found a bug caused by the following
Priority: P3
Component: other
Assignee: unassigned at gcc dot gnu.org
Reporter: mytbk920423 at gmail dot com
Target Milestone: ---
I use the following code get a 32-bit word from a byte array by loading each
byte and shifting them, but GCC doesn't optimize the co
: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: mytbk920423 at gmail dot com
Target Milestone: ---
When g++ builds following code, the function foo() referenced by this program
is compiled to symbol ``foo(VecReg&)``, w
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101385
--- Comment #2 from Iru Cai ---
Thanks, -gnatwe works for both gcc and gnatmake.
I see in the gnat_ugn manual that there is still the -Werror option that causes
GCC back end to treat warnings as errors. Is that means -gnatwe is for front
end, an
onent: ada
Assignee: unassigned at gcc dot gnu.org
Reporter: mytbk920423 at gmail dot com
Target Milestone: ---
I try to make the GCC Ada compiler error when there're warnings, but -Werror
doesn't work.
$ gcc -c -O2 -Werror test.adb && echo "Command return
: target
Assignee: unassigned at gcc dot gnu.org
Reporter: mytbk920423 at gmail dot com
Target Milestone: ---
Built with '-march=x86-64-v3 -O1', the following code generates a bsr
instruction, which has undefined behavior when the source operand is zero, thus
gives wr
IRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: mytbk920423 at gmail dot com
Target Milestone: ---
GCC doesn't warn on the following code when class B is a derived class.
-
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100347
Iru Cai changed:
What|Removed |Added
CC||mytbk920423 at gmail dot com
--- Comment #6
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97982
--- Comment #1 from Iru Cai ---
Hmm, I saw in the abs(3) that "Trying to take the absolute value of the most
negative integer is not defined."
But it's still strange to see a uint32->uint64_t cast results in a negative
value.
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: mytbk920423 at gmail dot com
Target Milestone: ---
The following code has different result when compiling with -O0/-O1 and -O2.
Also, ubsan will report an error. But I don't know why the
signed(INT_MIN)->unsig
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: mytbk920423 at gmail dot com
Target Milestone: ---
The following program cannot be compiled with g++ but can be compiled with
clang++ or any C compiler including gcc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87367
Iru Cai changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: mytbk920423 at gmail dot com
Target Milestone: ---
When compiling the following program with -Wnull-dereference, GCC doesn't warn
when using -O1, but warns when using -O2.
#include
ty
21 matches
Mail list logo
