ruby-core@ruby-lang.org archive (unofficial mirror)
 help / color / mirror / Atom feed
From: "jeremyevans0 (Jeremy Evans) via ruby-core" <ruby-core@ml.ruby-lang.org>
To: ruby-core@ml.ruby-lang.org
Cc: "jeremyevans0 (Jeremy Evans)" <noreply@ruby-lang.org>
Subject: [ruby-core:120535] [Ruby master Bug#21012] Compiling `a['a','b'],=1` with parse.y fails
Date: Tue, 07 Jan 2025 20:15:32 +0000 (UTC)	[thread overview]
Message-ID: <redmine.journal-111337.20250107201532.10330@ruby-lang.org> (raw)
In-Reply-To: <redmine.issue-21012.20250107184309.10330@ruby-lang.org>

Issue #21012 has been updated by jeremyevans0 (Jeremy Evans).

Backport changed from 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN to 3.1: REQUIRED, 3.2: REQUIRED, 3.3: REQUIRED, 3.4: REQUIRED

>From testing some historical versions on my system:

For: `a['a','b'],=1`

* Ruby 1.9-2.5: No segfault, looks to be correct instructions
* Ruby 2.6-3.1: Segfault
* Ruby 3.2: No segfault, but incorrect instructions
* Ruby 3.3-3.4: Segfault

For: `a['a',10],=1`:

* Ruby 1.9-2.5: No segfault, looks to be correct instructions
* Ruby 2.6-3.1: Segfault
* Ruby 3.2-3.4: No segfault, but incorrect instructions



----------------------------------------
Bug #21012: Compiling `a['a','b'],=1` with parse.y fails
https://bugs.ruby-lang.org/issues/21012#change-111337

* Author: tompng (tomoya ishida)
* Status: Open
* ruby -v: ruby 3.5.0dev (2025-01-06T01:50:53Z master c8e3d745fa) [x86_64-linux]
* Backport: 3.1: REQUIRED, 3.2: REQUIRED, 3.3: REQUIRED, 3.4: REQUIRED
----------------------------------------
Compiling this code with parse.y fails with segmentation fault.
~~~ruby
a['a','b'],=1
~~~

Compiling `a['a',x],=1` generates instruction sequence that wrong contains `opt_aset_with`.

~~~
$ ruby --parser=parse.y --dump=insn -e "a['a',999],=1"
== disasm: #<ISeq:<main>@-e:1 (1,0)-(1,13)>
0000 putself                                                          (   1)[Li]
0001 opt_send_without_block                 <calldata!mid:a, argc:0, FCALL|VCALL|ARGS_SIMPLE>
0003 putobject_INT2FIX_1_
0004 dup
0005 expandarray                            1, 0
0008 topn                                   1001
....
2006 topn                                   1001
2008 topn                                   1000
2010 opt_aset_with                          "a", <calldata!mid:[]=, argc:2, ARGS_SIMPLE>
2013 setn                                   1000
2015 pop
....
3014 pop
3015 leave
~~~





-- 
https://bugs.ruby-lang.org/
 ______________________________________________
 ruby-core mailing list -- ruby-core@ml.ruby-lang.org
 To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org
 ruby-core info -- https://ml.ruby-lang.org/mailman3/lists/ruby-core.ml.ruby-lang.org/

  reply	other threads:[~2025-01-07 20:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-07 18:43 [ruby-core:120531] " tompng (tomoya ishida) via ruby-core
2025-01-07 20:15 ` jeremyevans0 (Jeremy Evans) via ruby-core [this message]
2025-01-08  1:38 ` [ruby-core:120543] " jeremyevans0 (Jeremy Evans) via ruby-core
2025-01-15  1:56 ` [ruby-core:120688] " k0kubun (Takashi Kokubun) via ruby-core
2025-01-25  6:33 ` [ruby-core:120791] " nagachika (Tomoyuki Chikanaga) via ruby-core
2025-02-14  5:08 ` [ruby-core:121021] " k0kubun (Takashi Kokubun) via ruby-core

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=redmine.journal-111337.20250107201532.10330@ruby-lang.org \
    --to=ruby-core@ml.ruby-lang.org \
    --cc=noreply@ruby-lang.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 NNTP newsgroup(s).