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/102342] gm2 testsuite failures for non-default multilib
Date: Mon, 25 Oct 2021 11:41:43 +0000	[thread overview]
Message-ID: <bug-102342-4-UaNmSFOOdS@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102342-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #1 from Rainer Orth <ro at gcc dot gnu.org> ---
Created attachment 51660
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51660&action=edit
proposed patch

While testing a recent version of the modula-2 branch
(386e7057d75043439f313085c4cbde8109459915),
I developed the attached patch to fully address this issue, following the
prove-of-concept one already included.  With this patch, x86_64-pc-linux-gnu
testresults (both -m64 and -m32 multilibs) are clean with the exception of

Running target unix/-m32
FAIL: gm2/cpp/pass/subaddr.mod,  -O
FAIL: gm2/cpp/pass/subaddr.mod,  -O -g
FAIL: gm2/cpp/pass/subaddr.mod,  -O3 -fomit-frame-pointer
FAIL: gm2/cpp/pass/subaddr.mod,  -O3 -fomit-frame-pointer -finline-functions
FAIL: gm2/cpp/pass/subaddr.mod,  -Os
FAIL: gm2/cpp/pass/subaddr.mod,  -g

which is preexisting (PR modula2/102343).  On i386-pc-solaris2.11, there are a
few more failures, also preexisting.

  reply	other threads:[~2021-10-25 11:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-15  9:58 [Bug modula2/102342] New: " ro at gcc dot gnu.org
2021-10-25 11:41 ` ro at gcc dot gnu.org [this message]
2022-04-23 11:52 ` [Bug modula2/102342] " gaius at gcc dot gnu.org
2022-04-26  9:40 ` ro at CeBiTec dot Uni-Bielefeld.DE

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-102342-4-UaNmSFOOdS@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).