public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jbeulich at suse dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/115433] New: unexpected increase of testsuite execution time
Date: Tue, 11 Jun 2024 12:12:55 +0000	[thread overview]
Message-ID: <bug-115433-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 115433
           Summary: unexpected increase of testsuite execution time
           Product: gcc
           Version: 14.1.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libstdc++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: jbeulich at suse dot com
  Target Milestone: ---

With the usual, moderate increase of the number of tests it is somewhat
unexpected that a testsuite run now takes 50% more time for x86-64 targets, and
about 100% more for i686 targets (and there already with a 64-bit kernel
underneath). For comparison, taking a representative 64-bit system, testsuite
runs took
- gcc: a little over an hour
- g++: less than 40 min
- libstdc++: 3 hours
IOW what already took longest before has now further increased by a significant
percentage. (Absolute numbers are bigger on two or three generations older
hardware, but the relative values remain largely the same.)

All of this said - I certainly understand that moderate increases of overall
execution time is always to be expected for a new major release. It's just that
this time it's not quite "moderate" anymore.

             reply	other threads:[~2024-06-11 12:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-11 12:12 jbeulich at suse dot com [this message]
2024-06-11 12:43 ` [Bug libstdc++/115433] " redi at gcc dot gnu.org
2024-06-11 12:46 ` redi at gcc dot gnu.org
2024-06-11 12:50 ` jbeulich at suse dot com

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-115433-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: 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).