public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "roger at nextmovesoftware dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/113336] libatomic (testsuite) regressions on arm
Date: Thu, 25 Jan 2024 18:18:09 +0000 [thread overview]
Message-ID: <bug-113336-4-pag2V7puHf@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113336-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113336
Roger Sayle <roger at nextmovesoftware dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |NEW
Assignee|roger at nextmovesoftware dot com |unassigned at gcc dot gnu.org
Summary|libatomic (testsuite) |libatomic (testsuite)
|regressions on |regressions on arm
|armv6-linux-gnueabihf |
--- Comment #4 from Roger Sayle <roger at nextmovesoftware dot com> ---
Hi Victor,
Yes, I agree your approach is better/less invasive than mine. I simply copied
the existing idiom in Makefile.am, not noticing that this adds more
functionality to libatomic than is strictly required. Just adding the
missing/required tas_1_2_.lo is better (and hopefully more acceptable to the
maintainers/reviewers).
next prev parent reply other threads:[~2024-01-25 18:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-11 15:42 [Bug other/113336] New: libatomic (testsuite) regressions on armv6-linux-gnueabihf roger at nextmovesoftware dot com
2024-01-14 12:15 ` [Bug other/113336] " roger at nextmovesoftware dot com
2024-01-21 16:40 ` hp at gcc dot gnu.org
2024-01-25 17:09 ` victor.donascimento at arm dot com
2024-01-25 18:18 ` roger at nextmovesoftware dot com [this message]
2024-01-28 11:31 ` [Bug other/113336] libatomic (testsuite) regressions on arm doko at gcc dot gnu.org
2024-01-28 11:32 ` [Bug other/113336] [14 Regression] " doko at gcc dot gnu.org
2024-01-28 16:29 ` roger at nextmovesoftware dot com
2024-02-14 19:12 ` cvs-commit at gcc dot gnu.org
2024-02-17 16:45 ` roger at nextmovesoftware 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-113336-4-pag2V7puHf@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).