https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94021
--- Comment #7 from Martin Sebor ---
Since the merge with the sprintf pass, the strlen pass has an instance of EVRP
that it passes to sprintf to get range info from (it also uses it itself in
places).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83733
Martin Sebor changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
||msebor at gcc dot gnu.org
Resolution|--- |FIXED
--- Comment #4 from Martin Sebor ---
Neither test case triggers the warning in GCC 10. Bisection points to r269115
as the fix.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85741
Bug 85741 depends on bug 81401, which changed state.
Bug 81401 Summary: False positive sprintf warning at O2 (-Wformat-overflow)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81401
What|Removed |Added
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80776
Martin Sebor changed:
What|Removed |Added
Last reconfirmed|2017-05-16 00:00:00 |2020-3-4
See Also|
||2020-03-04
Assignee|unassigned at gcc dot gnu.org |msebor at gcc dot
gnu.org
Ever confirmed|0 |1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94004
Martin Sebor changed:
What|Removed |Added
Keywords||patch
--- Comment #6 from Martin Sebor -
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92478
Martin Sebor changed:
What|Removed |Added
Summary|[8 Regression] ICE: |[8 Regression] ICE on
|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93986
Martin Sebor changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94015
--- Comment #6 from Martin Sebor ---
(In reply to Nate Eldredge from comment #4)
A compile-time only test that doesn't depend on the target or endianness would
be much better than a runtime test that fails only on a subset of targets. The
way t
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90938
Martin Sebor changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
||msebor at gcc dot gnu.org
Known to fail||10.0, 7.3.0, 8.2.0, 9.1.0
--- Comment #2 from Martin Sebor ---
Reconfirmed for GCC 10.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94055
Martin Sebor changed:
What|Removed |Added
CC||msebor at gcc dot gnu.org
--- Comment #2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86691
Martin Sebor changed:
What|Removed |Added
Summary|missing -Warray-bounds due |missing -Warray-bounds on a
|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |msebor at gcc dot
gnu.org
--- Comment #3 from Martin Sebor ---
GCC accepts the invalid redeclaration of the built-in. GCC 8 silently, but GCC
9 and 10 diagnose it albeit only with -Wextra (see below
at gcc dot gnu.org |msebor at gcc dot
gnu.org
--- Comment #3 from Martin Sebor ---
I can put together a patch to define the assignment. Containers need to be
assignable in order to be used as elements in other containers or as members of
classes/structs that are. Otherwise, the limitation
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94040
Martin Sebor changed:
What|Removed |Added
Keywords||patch
Summary|[9/10 Regression
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: msebor at gcc dot gnu.org
Target Milestone: ---
The test case below shows GCC gets confused by the declarations of the template
instances below: it issues -Wmismatched-tags for the wrong
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: msebor at gcc dot gnu.org
Target Milestone: ---
Of the six declarations below each is accepted on its own. The latter two
redeclarations are accepted as well, but the first redeclaration
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94106
Martin Sebor changed:
What|Removed |Added
Summary|error on a function |[8/9/10 Regression] error
: other
Assignee: unassigned at gcc dot gnu.org
Reporter: msebor at gcc dot gnu.org
Target Milestone: ---
GCC exposes a number of attributes for transactional memory (see below) but the
documentation doesn't mention any of them.
The list of attributes from c-family/c-attr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94098
Martin Sebor changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |msebor at gcc dot
gnu.org
|1
Last reconfirmed||2020-03-10
CC||msebor at gcc dot gnu.org
Blocks||87403
--- Comment #1 from Martin Sebor ---
Confirmed with the output below. -Wterminate is fully
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94132
Martin Sebor changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Blocks|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69698
Bug 69698 depends on bug 94132, which changed state.
Bug 94132 Summary: Valid usage of flexible array member failing to compile
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94132
What|Removed |Added
-invalid-code |ice-on-valid-code
Assignee|unassigned at gcc dot gnu.org |msebor at gcc dot
gnu.org
--- Comment #4 from Martin Sebor ---
The code looks valid to me. It may be undefined because of the missing
initialization but with the VLA initialized the ICE is still there
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: msebor at gcc dot gnu.org
Target Milestone: ---
The declaration of the q member below is rejected with a parse error,
suggesting GCC is confused about what's
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84919
--- Comment #23 from Martin Sebor ---
I think that's a question for the release managers. I thought they like to
keep regressions open until all the affected branches have closed, but I could
be wrong. One way to find out is to close it and let
-end
Assignee: unassigned at gcc dot gnu.org
Reporter: msebor at gcc dot gnu.org
Target Milestone: ---
Bug 94157 was caused by modifying the string pointed to by the value returned
from getenv(), which is undefined according to both C and POSIX. C11 says in
7.22.4.8, p4:
The
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94040
Martin Sebor changed:
What|Removed |Added
Known to fail|10.0, 9.2.0 |9.3.0
Summary|[9/10 Regression
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: msebor at gcc dot gnu.org
Target Milestone: ---
The attribute machinery silently drops attributes from subsequent type
definitions. The test case below shows this with attribute nonnull but other
Priority: P3
Component: middle-end
Assignee: unassigned at gcc dot gnu.org
Reporter: msebor at gcc dot gnu.org
Target Milestone: ---
The following test case was derived from PR 94187. The past-the-end store in
f() is diagnosed by -Wstringop-overflow as
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90404
Martin Sebor changed:
What|Removed |Added
Target Milestone|--- |11.0
Component|c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94196
Martin Sebor changed:
What|Removed |Added
CC||msebor at gcc dot gnu.org
See
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80495
Martin Sebor changed:
What|Removed |Added
Known to fail|9.0 |10.0, 9.2.0
Last reconfirmed|2018-09-14
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81692
Martin Sebor changed:
What|Removed |Added
CC||msebor at gcc dot gnu.org
Known to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90404
Martin Sebor changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94169
Martin Sebor changed:
What|Removed |Added
Blocks|88781 |
--- Comment #1 from Martin Sebor ---
On
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94169
--- Comment #2 from Martin Sebor ---
Other C standard functions that return a pointer to an unmodifiable object:
localeconv(), setlocale(), strerror()
In addition, stdin, stdout, and stderr could be marked as pointing to read-only
(although u
Priority: P3
Component: middle-end
Assignee: unassigned at gcc dot gnu.org
Reporter: msebor at gcc dot gnu.org
Target Milestone: ---
GCC 10 diagnoses only one out of the three invalid uses of the unterminated
array below. The strlen pass "knows"
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92799
Martin Sebor changed:
What|Removed |Added
Known to work||10.0
Summary|[8/9/10 Regressio
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94131
Martin Sebor changed:
What|Removed |Added
Keywords||patch
--- Comment #5 from Martin Sebor -
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94098
Martin Sebor changed:
What|Removed |Added
Keywords||patch
--- Comment #3 from Martin Sebor -
|NEW
Ever confirmed|0 |1
CC||msebor at gcc dot gnu.org
Keywords||diagnostic
Last reconfirmed||2020-03-19
--- Comment #1 from Martin Sebor
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94078
Martin Sebor changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |msebor at gcc dot
gnu.org
|1
Last reconfirmed||2020-03-20
CC||msebor at gcc dot gnu.org
--- Comment #1 from Martin Sebor ---
I noticed this on x86_64-linux as well last night in a fully bootstrapped
compiler but today I can't repr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88433
Martin Sebor changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49330
Martin Sebor changed:
What|Removed |Added
CC||msebor at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82898
Martin Sebor changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
See Also|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94247
Martin Sebor changed:
What|Removed |Added
CC||msebor at gcc dot gnu.org
--- Comment #5
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=35587
Martin Sebor changed:
What|Removed |Added
Last reconfirmed|2008-03-17 14:05:57 |2020-3-23
Known to fail|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94247
--- Comment #7 from Martin Sebor ---
(In reply to Jakub Jelinek from comment #6)
> No, it diagnoses the main bug
Nope, it does not. -Wchar-subscripts is designed and documented to diagnose a
common cause of a bug. The actual bug itself (which,
Priority: P3
Component: middle-end
Assignee: unassigned at gcc dot gnu.org
Reporter: msebor at gcc dot gnu.org
Target Milestone: ---
-Wreturn-local-addr diagnoses only the first function below. It misses the
same problem in the second function. The root cause is
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94312
Martin Sebor changed:
What|Removed |Added
Summary|missing -Wreturn-local-addr |missing -Wreturn-local-addr
Priority: P3
Component: middle-end
Assignee: unassigned at gcc dot gnu.org
Reporter: msebor at gcc dot gnu.org
Target Milestone: ---
Modifying a const-qualified object or a string literal is undefined in both C
and C++ and can result in subtle bugs. Detecting attempts to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90404
Martin Sebor changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94313
--- Comment #2 from Martin Sebor ---
Removing invalid code not isn't wrong (as in non-conforming), but it's
decidedly unhelpful in avoiding the undefined behavior that doesn't necessarily
go away just because the invalid statement is gone. It ma
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94004
Martin Sebor changed:
What|Removed |Added
Known to work||10.0
Summary|[8/9/10 Regressio
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94313
--- Comment #4 from Martin Sebor ---
An implementation is free to do whatever it wants when it finds
invalid/undefined code. A quality implementation will also let the user know
about it so it can be fixed. An even better one will let the user
||msebor at gcc dot gnu.org
--- Comment #1 from Martin Sebor ---
This type of warning is new GCC 10; it was added in the commit below. It works
as designed here. It sees the following IL (the memset calls don't do
anything). The MEM[] = 65; statement is what trigge
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94335
--- Comment #5 from Martin Sebor ---
Few middle-end warnings consider control flow -- most simply look at a single
statement at a time and consider ranges of argument values (if any). Those
that do consider control flow (e.g., -Wreturn-local-add
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94338
Martin Sebor changed:
What|Removed |Added
CC||msebor at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94346
Martin Sebor changed:
What|Removed |Added
Keywords||ice-on-valid-code
--- Comment #2 from Mar
||10.0, 9.2.0
Assignee|unassigned at gcc dot gnu.org |msebor at gcc dot
gnu.org
--- Comment #3 from Martin Sebor ---
The change below avoids the ICE with no regressions in the attribute or warning
tests:
diff --git a/gcc/c-family/c-attribs.c b/gcc/c-family/c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94346
Martin Sebor changed:
What|Removed |Added
Keywords||patch
--- Comment #5 from Martin Sebor -
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94098
Martin Sebor changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94346
Martin Sebor changed:
What|Removed |Added
Known to work||10.0
Summary|[9/10 Regression]
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93824
Martin Sebor changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94078
Martin Sebor changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: msebor at gcc dot gnu.org
Target Milestone: ---
Similar to pr94313, the test case below shows that GCC silently eliminates some
statements that modify const scalars
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94374
Martin Sebor changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
||msebor at gcc dot gnu.org
Ever confirmed|0 |1
Severity|normal |enhancement
Status|UNCONFIRMED |NEW
--- Comment #1 from Martin Sebor ---
Confirmed.
C2X will likely have the same
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: msebor at gcc dot gnu.org
Target Milestone: ---
In the test case below, the subtraction can safely be folded to zero because a
is a restricted
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94428
Martin Sebor changed:
What|Removed |Added
CC||msebor at gcc dot gnu.org
||msebor at gcc dot gnu.org
Ever confirmed|0 |1
Status|UNCONFIRMED |WAITING
--- Comment #2 from Martin Sebor ---
Can you include a small test case that reproduce the problem (and the full
command line used to reproduce it
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=9
Martin Sebor changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94510
Martin Sebor changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |msebor at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94510
Martin Sebor changed:
What|Removed |Added
Keywords||patch
--- Comment #10 from Martin Sebor
|--- |11.0
Assignee|unassigned at gcc dot gnu.org |msebor at gcc dot
gnu.org
CC||msebor at gcc dot gnu.org
--- Comment #7 from Martin Sebor ---
I've actually been experimenting with this for GCC 11 as an extensi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94535
Martin Sebor changed:
What|Removed |Added
CC||msebor at gcc dot gnu.org
--- Comment #7
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94535
--- Comment #11 from Martin Sebor ---
Fred, the author of the paper, usually tests a number of compilers. In the
paper referenced from n2322 he mentions a bunch:
http://www.open-std.org/jtc1/sc22/wg14/www/docs/n1911.htm
: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: msebor at gcc dot gnu.org
Target Milestone: ---
I believe the two definitions of XB below are the same and should be accepted.
GCC for some
Priority: P3
Component: middle-end
Assignee: unassigned at gcc dot gnu.org
Reporter: msebor at gcc dot gnu.org
Target Milestone: ---
In the following (invalid) test case -Warray-bounds only diagnoses one of the
four out-of-bounds references, although it eliminates the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94580
Martin Sebor changed:
What|Removed |Added
Keywords||diagnostic
Blocks|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92326
Martin Sebor changed:
What|Removed |Added
Summary|wrong bound in zero-length |[10 Regression] wrong bound
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92828
Martin Sebor changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
||2020-04-13
Status|UNCONFIRMED |WAITING
CC||msebor at gcc dot gnu.org
--- Comment #7 from Martin Sebor ---
Waiting for a response to Martin's comment #4.
||msebor at gcc dot gnu.org
Ever confirmed|0 |1
Last reconfirmed||2020-04-13
--- Comment #21 from Martin Sebor ---
This is still unconfirmed, 7 years after it was reported. If there is an
outstanding bug it should be
|1
CC||msebor at gcc dot gnu.org
Status|UNCONFIRMED |WAITING
--- Comment #4 from Martin Sebor ---
I this (still) a problem today (if so, let's confirm it), otherwise let's
resolve it one way or the other.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90629
Martin Sebor changed:
What|Removed |Added
CC||msebor at gcc dot gnu.org
Ever
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78104
Martin Sebor changed:
What|Removed |Added
CC||bugzilla@poradnik-webmaster
|--- |DUPLICATE
See Also||https://gcc.gnu.org/bugzill
||a/show_bug.cgi?id=90629
CC||msebor at gcc dot gnu.org
--- Comment #4 from Martin Sebor ---
Per
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=30334
Bug 30334 depends on bug 81172, which changed state.
Bug 81172 Summary: Expected new warning option -Warray-bounds-pointer-arithmetic
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81172
What|Removed |Added
--
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56456
Bug 56456 depends on bug 81172, which changed state.
Bug 81172 Summary: Expected new warning option -Warray-bounds-pointer-arithmetic
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81172
What|Removed |Added
--
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81172
Martin Sebor changed:
What|Removed |Added
Known to work||10.0
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71218
Martin Sebor changed:
What|Removed |Added
CC||msebor at gcc dot gnu.org
--- Comment #4
||msebor at gcc dot gnu.org
Status|UNCONFIRMED |RESOLVED
--- Comment #4 from Martin Sebor ---
I can't reproduce an ICE with the attached translation unit so based on that
and on comment #3 resolving as worksforsome. Please reopen if it persists
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44004
Martin Sebor changed:
What|Removed |Added
CC||msebor at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83028
Martin Sebor changed:
What|Removed |Added
CC||msebor at gcc dot gnu.org
Last
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=30334
Martin Sebor changed:
What|Removed |Added
CC||msebor at gcc dot gnu.org
--- Comment
1 - 100 of 8151 matches
Mail list logo