public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug modula2/108183] wrong code generated in the modula2 scaffold mechanism
Date: Mon, 19 Dec 2022 23:57:20 +0000 [thread overview]
Message-ID: <bug-108183-4-mFmUy2i2jH@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108183-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108183
--- Comment #1 from Iain Sandoe <iains at gcc dot gnu.org> ---
example:
a-hello.s:217:2: error: symbol '__M2_termios_ctor' can not be undefined in a
subtraction expression
leal __M2_termios_ctor-L5$pb(%eax), %edx #, _T53_57
(lldb) p (void) debug_tree(decl)
<function_decl 0x1068c5100 _M2_termios_ctor
type <function_type 0x106829dc8
type <void_type 0x1068250a8 PROC VOID
align:8 warn_if_not_align:0 symtab:0 alias-set -1 canonical-type
0x1068250a8
pointer_to_this <pointer_type 0x106825150 ADDRESS>>
QI
size <integer_cst 0x106802d98 constant 8>
unit-size <integer_cst 0x106802db0 constant 1>
align:8 warn_if_not_align:0 symtab:0 alias-set -1 canonical-type
0x106829dc8
arg-types <tree_list 0x10681cde8 value <void_type 0x1068250a8 PROC>>
pointer_to_this <pointer_type 0x106850dc8>>
addressable public static QI (null):0:0 align:8 warn_if_not_align:0 context
<translation_unit_decl 0x10680d168 D.46>
(mem:QI (symbol_ref:SI ("_M2_termios_ctor") <function_decl 0x1068c5100
_M2_termios_ctor>) [0 S1 A8]) chain <function_decl 0x1068c5000 _M2_RTco_fini>>
next prev parent reply other threads:[~2022-12-19 23:57 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-19 23:45 [Bug modula2/108183] New: " iains at gcc dot gnu.org
2022-12-19 23:46 ` [Bug modula2/108183] " iains at gcc dot gnu.org
2022-12-19 23:57 ` iains at gcc dot gnu.org [this message]
2022-12-20 8:20 ` gaius at gcc dot gnu.org
2022-12-20 8:38 ` gaius at gcc dot gnu.org
2022-12-20 9:36 ` iains at gcc dot gnu.org
2022-12-20 10:00 ` iains at gcc dot gnu.org
2022-12-20 12:34 ` iains at gcc dot gnu.org
2022-12-20 12:37 ` iains at gcc dot gnu.org
2022-12-20 12:45 ` rguenth at gcc dot gnu.org
2022-12-20 20:21 ` iains at gcc dot gnu.org
2022-12-20 20:42 ` iains at gcc dot gnu.org
2022-12-20 21:24 ` gaius at gcc dot gnu.org
2022-12-21 15:35 ` iains at gcc dot gnu.org
2022-12-21 15:39 ` iains at gcc dot gnu.org
2022-12-24 17:19 ` iains at gcc dot gnu.org
2022-12-28 16:07 ` gaius at gcc dot gnu.org
2022-12-31 12:54 ` iains at gcc dot gnu.org
2022-12-31 12:57 ` iains at gcc dot gnu.org
2023-01-01 9:29 ` cvs-commit at gcc dot gnu.org
2023-01-02 11:21 ` iains at gcc dot gnu.org
2023-01-02 12:20 ` iains at gcc dot gnu.org
2023-01-04 14:55 ` cvs-commit at gcc dot gnu.org
2023-01-04 16:22 ` iains 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-108183-4-mFmUy2i2jH@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).