public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/108505] [13 Regression] Arm: arm-none-eabi toolchain build failing with compiler error. Date: Tue, 24 Jan 2023 09:58:41 +0000 [thread overview] Message-ID: <bug-108505-4-VwonUIwpug@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108505-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108505 --- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by SRINATH PARVATHANENI <sripar01@gcc.gnu.org>: https://gcc.gnu.org/g:275820c09e5f397040cbff69c90012dc1e220faf commit r13-5322-g275820c09e5f397040cbff69c90012dc1e220faf Author: Srinath Parvathaneni <srinath.parvathaneni@arm.com> Date: Tue Jan 24 09:57:52 2023 +0000 arm: Fix inclusion of arm-mlib.h header more than once (pr108505). The patch fixes the build issue for arm-none-eabi target configured with --with-multilib-list=aprofile,rmprofile, in which case the header file arm/arm-mlib.h is being included more than once and the toolchain build is failing (PR108505). gcc/ChangeLog: 2023-01-24 Srinath Parvathaneni <srinath.parvathaneni@arm.com> PR target/108505 * config.gcc (tm_file): Move the variable out of loop.
next prev parent reply other threads:[~2023-01-24 9:58 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-23 18:04 [Bug c/108505] New: " srinath.parvathaneni at arm dot com 2023-01-23 18:07 ` [Bug target/108505] [13 Regression] " pinskia at gcc dot gnu.org 2023-01-23 18:27 ` pinskia at gcc dot gnu.org 2023-01-23 18:33 ` srinath.parvathaneni at arm dot com 2023-01-23 18:34 ` srinath.parvathaneni at arm dot com 2023-01-23 18:40 ` pinskia at gcc dot gnu.org 2023-01-24 9:58 ` cvs-commit at gcc dot gnu.org [this message] 2023-01-24 10:04 ` srinath.parvathaneni at arm dot com 2023-02-08 18:40 ` 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-108505-4-VwonUIwpug@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).