public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "nightstrike at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/102060] New: -Wprio-ctor-dtor underlines the wrong part of the source line
Date: Wed, 25 Aug 2021 10:13:53 +0000	[thread overview]
Message-ID: <bug-102060-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 102060
           Summary: -Wprio-ctor-dtor underlines the wrong part of the
                    source line
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: other
          Assignee: unassigned at gcc dot gnu.org
          Reporter: nightstrike at gmail dot com
  Target Milestone: ---

We get a warning when building for windows that should be fixed, but it
highlights that the warning is slightly mistaken about where the problem is:

gcc-git/libgcc/config/i386/cygming-crtend.c:59:1: warning: constructor
priorities from 0 to 100 are reserved for the implementation [-Wprio-ctor-dtor]
   59 | static void register_frame_ctor (void) __attribute__ ((constructor
(0)));
      | ^~~~~~


The word "static" is underlined, but I presume that instead it should be
"constructor(0)".

             reply	other threads:[~2021-08-25 10:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-25 10:13 nightstrike at gmail dot com [this message]
2021-08-25 10:17 ` [Bug c/102060] " pinskia at gcc dot gnu.org
2021-08-25 15:44 ` msebor at gcc dot gnu.org
2021-08-25 15:46 ` [Bug c/102060] -Wprio-ctor-dtor underlines the wrong part of the source line due to missing location for attributes msebor 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-102060-4@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).