public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug modula2/102343] New: gm2/cpp/pass/subaddr.mod FAILs for non-default multilib Date: Wed, 15 Sep 2021 11:15:06 +0000 [thread overview] Message-ID: <bug-102343-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102343 Bug ID: 102343 Summary: gm2/cpp/pass/subaddr.mod FAILs for non-default multilib Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: modula2 Assignee: unassigned at gcc dot gnu.org Reporter: ro at gcc dot gnu.org CC: gaiusmod2 at gmail dot com Target Milestone: --- The gm2/cpp/pass/subaddr.mod test FAILs for non-default multilibs (seen on x86_64-pc-linux-gnu with -m32 and i386-pc-solaris2.11 with -m64): FAIL: gm2/cpp/pass/subaddr.mod, -g FAIL: gm2/cpp/pass/subaddr.mod, -O FAIL: gm2/cpp/pass/subaddr.mod, -O -g FAIL: gm2/cpp/pass/subaddr.mod, -Os FAIL: gm2/cpp/pass/subaddr.mod, -O3 -fomit-frame-pointer FAIL: gm2/cpp/pass/subaddr.mod, -O3 -fomit-frame-pointer -finline-functions /vol/gcc/src/git/modula-2/gcc/testsuite/gm2/cpp/pass/subaddr.mod:34:1: error: can only CAST objects of the same size Unfortunately, -save-temps has no effect so one cannot see what actual input is passed to cc1gm2. Besides, it seems weird to special-case x86_64 and 64-bit alpha (was there ever a 32-bit port?) when every 64-bit target would already be handled by __LP64__.
next reply other threads:[~2021-09-15 11:15 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-09-15 11:15 ro at gcc dot gnu.org [this message] 2023-01-17 15:18 ` [Bug modula2/102343] " iains at gcc dot gnu.org 2023-01-17 16:52 ` iains at gcc dot gnu.org 2023-01-22 0:22 ` iains at gcc dot gnu.org 2023-01-25 15:24 ` cvs-commit at gcc dot gnu.org 2023-01-25 15:45 ` iains at gcc dot gnu.org 2023-01-27 8:48 ` cvs-commit 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-102343-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: linkBe 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).