public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/96383] [8/9/10/11 Regression] Full ABI information missing from GCC compiled C
Date: Fri, 31 Jul 2020 08:28:45 +0000 [thread overview]
Message-ID: <bug-96383-4-HdZUe6nCi1@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96383-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96383
--- Comment #13 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to Eric Botcazou from comment #12)
> > So with the attached 'updated patch' I see
> >
> > === gnat tests ===
> >
> >
> > Running target unix/
> > FAIL: gnat.dg/debug11_pkg.adb scan-assembler-not foreign_imported_func
> > FAIL: gnat.dg/debug9.adb scan-assembler-times \\\\(DIE \\\\(0x[a-f0-9]*\\\\)
> > DW_
> > TAG_type_unit\\\\) 0
> >
> > where the first FAIL seems obvious from the name of 'foreign_imported_func'
> > and the changed outcome is expected and OK?
>
> The annoying thing is the discrepancy with the variable case; in other
> words, the patch is undercutting gnat_write_global_declarations
> (utils.c:5913).
So, for Ada, would you like to preserve current behavior rather than what
Richard's patch does?
If so, can't we have a langhook that decides that?
I don't know much about Ada, but would think that having the prototypes even
for functions defined in other shared libraries if they are called or
referenced in the TU is useful even for Ada.
next prev parent reply other threads:[~2020-07-31 8:28 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-29 21:20 [Bug c/96383] New: Full ABI information missing " woodard at redhat dot com
2020-07-29 21:23 ` [Bug c/96383] " woodard at redhat dot com
2020-07-29 21:23 ` woodard at redhat dot com
2020-07-30 3:52 ` [Bug debug/96383] " woodard at redhat dot com
2020-07-30 6:14 ` [Bug debug/96383] [8/9/10/11 Regression] " rguenth at gcc dot gnu.org
2020-07-30 8:24 ` rguenth at gcc dot gnu.org
2020-07-30 9:01 ` jakub at gcc dot gnu.org
2020-07-30 9:06 ` rguenther at suse dot de
2020-07-30 9:09 ` jakub at gcc dot gnu.org
2020-07-30 9:34 ` rguenth at gcc dot gnu.org
2020-07-30 12:34 ` [Bug debug/96383] [8/9/10/11 Regression] Full ABI information " rguenth at gcc dot gnu.org
2020-07-30 13:29 ` rguenth at gcc dot gnu.org
2020-07-31 8:23 ` ebotcazou at gcc dot gnu.org
2020-07-31 8:28 ` jakub at gcc dot gnu.org [this message]
2020-07-31 8:43 ` rguenth at gcc dot gnu.org
2020-07-31 8:49 ` jakub at gcc dot gnu.org
2020-07-31 8:51 ` ebotcazou at gcc dot gnu.org
2020-07-31 8:52 ` rguenther at suse dot de
2020-07-31 9:00 ` jakub at gcc dot gnu.org
2020-07-31 9:10 ` rguenther at suse dot de
2020-07-31 9:15 ` jakub at gcc dot gnu.org
2020-07-31 10:04 ` rguenther at suse dot de
2020-07-31 12:04 ` ebotcazou at gcc dot gnu.org
2020-07-31 12:10 ` jakub at gcc dot gnu.org
2020-07-31 12:23 ` rguenther at suse dot de
2020-07-31 13:19 ` cvs-commit at gcc dot gnu.org
2020-07-31 13:20 ` [Bug debug/96383] [8/9/10 " rguenth at gcc dot gnu.org
2020-07-31 13:20 ` rguenth at gcc dot gnu.org
2020-08-02 18:42 ` slyfox at gcc dot gnu.org
2020-12-02 12:17 ` aoliva at gcc dot gnu.org
2020-12-02 12:27 ` rguenther at suse dot de
2021-04-30 8:07 ` rguenth at gcc dot gnu.org
2021-05-14 9:53 ` [Bug debug/96383] [9/10 " jakub at gcc dot gnu.org
2021-06-01 8:18 ` rguenth at gcc dot gnu.org
2022-05-27 9:43 ` [Bug debug/96383] [10 " rguenth at gcc dot gnu.org
2022-06-28 10:41 ` jakub at gcc dot gnu.org
2023-07-07 8:59 ` rguenth 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-96383-4-HdZUe6nCi1@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).