public inbox for [email protected]  

help / color / mirror / Atom feed

From: Tom Lane <[email protected]>
To: Bruce Momjian <[email protected]>
Cc: John Naylor <[email protected]>
Cc: David Rowley <[email protected]>
Cc: PostgreSQL-development <[email protected]>
Subject: Re: Debian 12 gcc warning
Date: Tue, 29 Aug 2023 23:30:06 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <ZO6u1hySX4lBI/[email protected]>
References: <[email protected]>
	<CAApHDvosmrsBB=vJDEwxsAJhdrLXvT-JTPOHw3DG+ERv0w-M7Q@mail.gmail.com>
	<CAFBsxsFbNiq-S9VyBmon7J43q_pkSBgyCqWnhwj=Get51jfcAA@mail.gmail.com>
	<[email protected]>
	<[email protected]>
	<ZO6u1hySX4lBI/[email protected]>

Bruce Momjian <[email protected]> writes:
> On Tue, Aug 29, 2023 at 10:18:36AM -0400, Tom Lane wrote:
>> That seems like a pretty clear compiler bug, particularly since it just
>> appears in this one version.  Rather than contorting our code, I'd
>> suggest filing a gcc bug.

> I assume I have to create a test case to report this to the gcc team.  I
> tried to create such a test case on gcc 12 but it doesn't generate the
> warning.  Attached is my attempt.  Any ideas?  I assume we can't just
> tell them to download our software and compile it.

IIRC, they'll accept preprocessed compiler input for the specific file;
you don't need to provide a complete source tree.  Per
https://gcc.gnu.org/bugs/

    Please include all of the following items, the first three of which can be obtained from the output of gcc -v:

    the exact version of GCC;
    the system type;
    the options given when GCC was configured/built;
    the complete command line that triggers the bug;
    the compiler output (error messages, warnings, etc.); and
    the preprocessed file (*.i*) that triggers the bug, generated by adding -save-temps to the complete compilation command, or, in the case of a bug report for the GNAT front end, a complete set of source files (see below).

Obviously, if you can trim the input it's good, but it doesn't
have to be a minimal reproducer.

			regards, tom lane

view thread (8+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Debian 12 gcc warning
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox