https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117809
--- Comment #2 from felix-gcc at fefe dot de ---
Another real-world example is asprintf from GNU libc:
int asprintf(char **restrict strp, const char *restrict fmt, ...);
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119353
--- Comment #2 from felix-gcc at fefe dot de ---
I ran rustup update stable.
$ rustc --version
rustc 1.85.0 (4d91de4e4 2025-02-17)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119353
Bug ID: 119353
Summary: build failure: error[E0554]: `#![feature]` may not be
used on the stable release channel
Product: gcc
Version: 15.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117810
--- Comment #2 from felix-gcc at fefe dot de ---
Hmm, now that you mention it explicitly... Just like C++ iterators, max does
not actually point at the last element in the array but at the first element
behind the array.
That appears to be more
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117810
Bug ID: 117810
Summary: Feature request: attribute access but for (start, end)
type interfaces
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117809
Bug ID: 117809
Summary: feature request: attribute malloc but for
non-function-return-value return values
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Severi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117807
Bug ID: 117807
Summary: analyzer gets confused by integer promotion
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: anal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114658
felix-gcc at fefe dot de changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|-
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114658
--- Comment #2 from felix-gcc at fefe dot de ---
I'm probably doing something really stupid wrong, sorry for the noise.
Here's what I'm doing:
$ git checkout releases/gcc-13
Switched to branch 'releases/gcc-13'
$ git branch
master
* releases/
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114658
Bug ID: 114658
Summary: branch "releases/gcc-13" builds "gcc version 14.0.1
(experimental)"
Product: gcc
Version: 13.2.1
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107614
felix-gcc at fefe dot de changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|-
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107614
Bug ID: 107614
Summary: build goes through but make install fails
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: other
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105728
--- Comment #4 from felix-gcc at fefe dot de ---
If you do have a printf that references debug_cnt, it wouldn't be removed,
right?
If you expect unreferenced variables to not be optimized out, you can always
compile without optimizer. For local
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105728
Bug ID: 105728
Summary: dead store to static var not optimized out
Product: gcc
Version: 11.3.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100294
Bug ID: 100294
Summary: need attribute takes_ownership
Product: gcc
Version: 11.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: analyzer
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98460
Bug ID: 98460
Summary: _builtin_cpu_supports("sha") missing
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
16 matches
Mail list logo