public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug modula2/108119] m2rte Seems like it should not be there at all
Date: Thu, 15 Dec 2022 08:35:40 +0000	[thread overview]
Message-ID: <bug-108119-4-9Y7rrytSb4@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108119-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108119

--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
It looks to me the plugin isn't needed to compile m2 programs, it's merely an
additional tool to diagnose invalid code (that is maybe never be reached at
runtime).  So I'd suggest to put this plugin use behind some driver option.

Alternatively the functionality could be lifted to the middle-end for example
by introducing an __attribute__((diagnose_if_invoked_on_function_entry))
that could then emit

warning: 'error' is always invoked when executing 'foo'

for

void __attribute__((diagnose_if_invoked_on_function_entry)) error ();

void foo ()
{
  error ();
}

but I understand the plugin does some whole-program analysis?  That won't
work with LTO at the point the plugin runs.

That said, the immediate thing to do would be to make the plugin build/run
dependent on plugin support.

  reply	other threads:[~2022-12-15  8:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-15  8:04 [Bug modula2/108119] New: " pinskia at gcc dot gnu.org
2022-12-15  8:35 ` rguenth at gcc dot gnu.org [this message]
2022-12-20 12:12 ` [Bug modula2/108119] " gaius at gcc dot gnu.org
2022-12-20 12:13 ` gaius at gcc dot gnu.org
2023-08-10  0:46 ` [Bug modula2/108119] m2rte plugin should be disabled by default egallager at gcc dot gnu.org
2023-08-12  3:48 ` gaius at gcc dot gnu.org
2023-08-12 12:44 ` cvs-commit at gcc dot gnu.org
2023-08-12 12:53 ` cvs-commit at gcc dot gnu.org
2023-08-12 12:58 ` gaius at gcc dot gnu.org

Reply instructions:

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

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

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-108119-4-9Y7rrytSb4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).