Hello,
I played some more with odd programs and the effect on control flow
graph construction (as a part of condition coverage support [1]) and
came across this:
int fn (int a, int b, int c) {
int x = 0;
if (a && b) {
if (c) {
goto a_;
} else {
On Fri, Sep 2, 2022 at 11:50 AM Jørgen Kvalsvik wrote:
>
>
> Hello,
>
> I played some more with odd programs and the effect on control flow
> graph construction (as a part of condition coverage support [1]) and
> came across this:
>
> int fn (int a, int b, int c) {
> int x = 0;
> if (a &
Keith Packard via Gcc-patches writes:
> Picolibc is a C library for embedded systems based on code from newlib
> and avr libc. To connect some system-dependent picolibc functions
> (like stdio) to an underlying platform, the platform may provide an OS
> library.
>
> This OS library must follow the
Given that pdp11 no longer supports debug output, I get a lot more test
failures, like this:
spawn -ignore SIGHUP /Users/pkoning/Documents/svn/build/pdp/gcc/xgcc
-B/Users/pkoning/Documents/svn/build/pdp/gcc/ -mlra -fdiagnostics-plain-output
-Og -g -w -c -o 2105-1.o
/Users/pkoning/Documents
Hi!
(Currently still on parental leave, but I just had to...) ;-P
On 2022-05-15T01:02:07+0200, Jan Hubicka via Gcc wrote:
> We are pleased to invite you all to the next GNU Tools Cauldron,
> taking place in [Prague] on September 16-18, 2022. We are looking forward
> to meet you again after thr
Hi JeanHeyd,
Subject: Re: [PATCH] Various pages: SYNOPSIS: Use VLA syntax in
function parameters
Date: Fri, 2 Sep 2022 16:56:00 -0400
From: JeanHeyd Meneide
To: Alejandro Colomar
CC: Ingo Schwarze , linux-...@vger.kernel.org
Hi Alejandro and Ingo,
Just chiming i
Snapshot gcc-11-20220902 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/11-20220902/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 11 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
Richard Sandiford writes:
Thanks much for reviewing this series. I really appreciate it.
> should there be a default case that raises an error for unrecognised
> libcs? Command-line checking for configure isn't very tight, but we
> do raise similar errors for things like invalid --enable-
