Snapshot gcc-12-20220130 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/12-20220130/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 12 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
On Sun, 2022-01-30 at 01:09 +, Jonathan Wakely via Gcc wrote:
> On Sat, 29 Jan 2022, 20:25 Søren Holm via Gcc, wrote:
>
> > Hi
> >
> > I believe I have found some kind of bug in GCC. The target is a
> > cortex-m7 CPU. I do not have an isolated test software so I'm
> > thinking
> > of bisecti
Meta-comment: a subject line of "Enquiry" is very vague, and most commonly
used by spammers and phishers. Your enquiry is about undefined behaviour
due to a missing return, which would have been a much better subject.
On Sun, 30 Jan 2022, 09:48 Theodore Papadopoulo, <
theodore.papadopo...@inria
On Sun, 30 Jan 2022, 10:58 Jakub Jelinek, wrote:
> On Sun, Jan 30, 2022 at 10:50:56AM +, Jonathan Wakely wrote:
> > We could put a trap instruction at the end of the function though, which
> > would make the result a bit less arbitrary.
> >
> > I've come around to thinking that's preferable f
On Sun, Jan 30, 2022 at 10:50:56AM +, Jonathan Wakely wrote:
> We could put a trap instruction at the end of the function though, which
> would make the result a bit less arbitrary.
>
> I've come around to thinking that's preferable for cases like this.
Depends on which exact cases.
Because f
On Sun, 30 Jan 2022, 10:42 Jakub Jelinek via Gcc, wrote:
> On Sun, Jan 30, 2022 at 10:47:41AM +0100, Theodore Papadopoulo wrote:
> > Before creating a bug report, I want to check with the GCC community (all
> > the more that checking that the problem has not yet been reported is
> > complicated a
On Sun, Jan 30, 2022 at 10:47:41AM +0100, Theodore Papadopoulo wrote:
> Before creating a bug report, I want to check with the GCC community (all
> the more that checking that the problem has not yet been reported is
> complicated at leat for me).
>
> The following (admitedly buggy) program genera
Before creating a bug report, I want to check with the GCC community
(all the more that checking that the problem has not yet been reported
is complicated at leat for me).
The following (admitedly buggy) program generates a segmentation
violation on fedora 35 (this is with g++ 11.2.1 20211203
