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: Wed, 21 Dec 2022 15:35:47 +0000	[thread overview]
Message-ID: <bug-108183-4-7E7icaCBih@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 #12 from Iain Sandoe <iains at gcc dot gnu.org> ---
With the change above (and adding an assert that the function is not
defined/implemented) -- NOTE: plus a number of other hacks to workaround other
PRs in progress ... we now have something more reasonable for m32 darwin.

test time is large - primarily because a significant number of the fails are
timeouts.


=== x86-64 Darwin with a 32b multilib.

                === gm2 Summary for unix/-m32 ===

# of expected passes            11820
# of unexpected failures        48

                === gm2 Summary for unix/-m64 ===

# of expected passes            11818
# of unexpected failures        50

                === gm2 Summary ===

# of expected passes            23638
# of unexpected failures        98

Compiler version: gcc gm2 
Platform: x86_64-apple-darwin17

==== i686-darwin with a 64b multilib.

                === gm2 Summary for unix/-m32 ===

# of expected passes            11833
# of unexpected failures        35

                === gm2 Summary for unix/-m64 ===

# of expected passes            12957
# of unexpected failures        63

                === gm2 Summary ===

# of expected passes            24790
# of unexpected failures        98

Compiler version: gcc gm2 
Platform: i686-apple-darwin9

===== powerpc-darwin

                === gm2 Summary for unix/-m32 ===

# of expected passes            11817
# of unexpected failures        51

                === gm2 Summary for unix/-m32 ===

# of expected passes            11817
# of unexpected failures        51

  parent reply	other threads:[~2022-12-21 15:35 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
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 [this message]
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-7E7icaCBih@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).