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/91602] GCC fails to build for riscv in a combined tree due to misconfigured leb128 support
Date: Fri, 20 Aug 2021 21:29:27 +0000	[thread overview]
Message-ID: <bug-91602-4-57cwZRqdlY@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-91602-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #16 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Sergey Belyshev <ssb@gcc.gnu.org>:

https://gcc.gnu.org/g:7cad8a8f9f7bfa8e98f6a0615541f589fd1d3fc1

commit r12-3047-g7cad8a8f9f7bfa8e98f6a0615541f589fd1d3fc1
Author: Serge Belyshev <belyshev@depni.sinp.msu.ru>
Date:   Fri Jul 16 10:52:33 2021 +0300

    configure: drop version checks for in-tree gas [PR91602]

    Special-casing checks for in-tree gas features is unnecessary since
    r100007 which made configure-gcc depend on all-gas, and thus making
    alternate code path in gcc_GAS_CHECK_FEATURE for in-tree gas
    redundant.

    Along the way this fixes PR 91602, which is caused by incorrect guess
    of leb128 support presence in RISC-V.

    First patch removes alternate code path in gcc_GAS_CHECK_FEATURE and
    related code, the rest are further cleanups.  Patches 2 and 3 in
    series make no functional changes, thus configure is unchanged.

    gcc/ChangeLog:

            PR target/91602
            * acinclude.m4 (_gcc_COMPUTE_GAS_VERSION,
_gcc_GAS_VERSION_GTE_IFELSE)
            (gcc_GAS_VERSION_GTE_IFELSE): Remove.
            (gcc_GAS_CHECK_FEATURE): Do not handle in-tree case specially.
            * configure.ac: Remove gcc_cv_gas_major_version,
gcc_cv_gas_minor_version.
            Remove remaining checks for in-tree assembler.
            * configure: Regenerate.

  parent reply	other threads:[~2021-08-20 21:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-91602-4@http.gcc.gnu.org/bugzilla/>
2021-07-16  8:06 ` belyshev at depni dot sinp.msu.ru
2021-07-16  8:24 ` jakub at gcc dot gnu.org
2021-07-19 14:40 ` wilson at gcc dot gnu.org
2021-07-21 14:59 ` belyshev at depni dot sinp.msu.ru
2021-08-20 21:29 ` cvs-commit at gcc dot gnu.org [this message]
2021-08-20 21:34 ` belyshev at depni dot sinp.msu.ru

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-91602-4-57cwZRqdlY@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).