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: Wed, 08 Feb 2023 18:40:39 +0000	[thread overview]
Message-ID: <bug-108505-4-Lq3ItR8Ad4@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 #7 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:2eeda82d6288fb2a8fbc302d98ed51337e01aaaa

commit r13-5744-g2eeda82d6288fb2a8fbc302d98ed51337e01aaaa
Author: Srinath Parvathaneni <srinath.parvathaneni@arm.com>
Date:   Wed Feb 8 18:39:06 2023 +0000

    arm: Optimize arm-mlib.h header inclusion [pr108505].

    I have committed a fix [1] into gcc trunk for a build
    issue mentioned in pr108505 and latter received few upstream
    comments proposing more robust fix for this issue.

    In this patch I'm addressing those comments and sending this
    as a followup patch.

    gcc/ChangeLog:

    2023-01-27  Srinath Parvathaneni  <srinath.parvathaneni@arm.com>

            PR target/108505
            * config.gcc (tm_mlib_file): Define new variable.

      parent reply	other threads:[~2023-02-08 18:40 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
2023-01-24 10:04 ` srinath.parvathaneni at arm dot com
2023-02-08 18:40 ` cvs-commit at gcc dot gnu.org [this message]

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-Lq3ItR8Ad4@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).