Snapshot gcc-14-20240421 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/14-20240421/
and on various mirrors, see https://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 14 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
I have two simple questions, I hope!
1. Is there a set of flags that, when compiling gcc, is meant to
produce no warnings? I get a surfeit of warnings with my particular
favorite options.
2. Are the libgcc functions warning_at() and error_at() intended for
use by all front-ends? As of now,
On Sun, Apr 21, 2024 at 10:40:14PM +0200, Alejandro Colomar wrote:
> On Sun, Apr 21, 2024 at 05:30:52PM +0200, Mark Wielaard wrote:
> > Hi Alejandro,
>
> Hi Mark,
>
> I've reordered your message, to organize my response.
>
> > On Wed, Apr 10, 2024 at 06:30:42PM +0200, Alejandro Colomar wrote:
>
On Sun, Apr 21, 2024 at 05:30:52PM +0200, Mark Wielaard wrote:
> Hi Alejandro,
Hi Mark,
I've reordered your message, to organize my response.
> On Wed, Apr 10, 2024 at 06:30:42PM +0200, Alejandro Colomar wrote:
> > It would also be interesting to require showing range-diffs between
> > patch rev
Hi Alejandro,
On Wed, Apr 10, 2024 at 06:30:42PM +0200, Alejandro Colomar wrote:
> It would also be interesting to require showing range-diffs between
> patch revisions. They make it much more difficult to introduce a
> vulnerability after a reviewer has turned its mins into approving the
> patch
