kotovalexarian-likes-github/ruby--ruby
1
0
Fork 0
mirror of https://github.com/ruby/ruby.git synced 2022-11-09 12:17:21 -05:00
Code Releases Activity

YJIT: Improve checking message for rustc version (#6693)

Browse source 
Preivously we didn't have a "checking ...." line for this check and when
rustc was too old, we would dump the error message to the console like:

    checking for rustc... rustc
    error: there is no argument named `x`
     --> <anon>:1:33
      |
    1 | fn main() { let x = 1; format!("{x}"); }
      |                                 ^^^

    error: aborting due to previous error

`configure` checks usually don't do this and this might be confusing.

With this commit it now says something like:

    checking whether rustc is new enough for YJIT... no
This commit is contained in:
Alan Wu 2022-11-08 15:29:30 -05:00 committed by GitHub
parent 1a65ab20cb
commit 1466682a23
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
Notes: git 2022-11-08 20:29:48 +00:00 
Merged-By: maximecb <maximecb@ruby-lang.org>
1 changed files with 3 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
configure.ac
View file

@ -3738,9 +3738,11 @@ AC_CHECK_PROG(RUSTC, [rustc], [rustc], [no]) dnl no ac_tool_prefix
dnl check if rustc is recent enough to build YJIT (rustc >= 1.58.0) dnl check if rustc is recent enough to build YJIT (rustc >= 1.58.0)
YJIT_RUSTC_OK=no YJIT_RUSTC_OK=no
AS_IF([test "$RUSTC" != "no"], AS_IF([test "$RUSTC" != "no"],
AS_IF([echo "fn main() { let x = 1; format!(\"{x}\"); }" | $RUSTC - --emit asm=/dev/null], AC_MSG_CHECKING([whether ${RUSTC} is new enough for YJIT])
AS_IF([echo "fn main() { let x = 1; format!(\"{x}\"); }" | $RUSTC - --emit asm=/dev/null 2>/dev/null],
[YJIT_RUSTC_OK=yes] [YJIT_RUSTC_OK=yes]
) )
AC_MSG_RESULT($YJIT_RUSTC_OK)
) )
dnl check if we can build YJIT on this target platform dnl check if we can build YJIT on this target platform