December 2023 - ruby-core - ml.ruby-lang.org

[ruby-core:111988] [Ruby master Feature#19370] Anonymous parameters for blocks?
by zverok (Victor Shepelev) 23 Dec '23

23 Dec '23

Issue #19370 has been reported by zverok (Victor Shepelev). ---------------------------------------- Feature #19370: Anonymous parameters for blocks? https://bugs.ruby-lang.org/issues/19370 * Author: zverok (Victor Shepelev) * Status: Open * Priority: Normal ---------------------------------------- Just to clarify: are anonymous parameters delegation is planned to support in blocks? It would be a nice addition, if it is possible to implement: ```ruby # data in form [request method, URL, params]: [ [:get, 'https://google.com', {q: 'Ruby'}, {'User-Argent': 'Google-Chrome'}], [:post, 'https://gist.github.com', 'body'], # ... ].each { |method, *| request(method.to_s.upcase, *) } ``` ...and at the very least, consistent with what the method definition can have. If they are NOT planned to be implemented, I believe that at least error messages should be made much clearer, because currently, this would happen while running the code above: > no anonymous rest parameter (SyntaxError) I understand the reason (the `request` clause doesn't "see" anonymous parameter of the **block**, and claims that current **method** doesn't have them), but it looks honestly confusing and inconsistent. -- https://bugs.ruby-lang.org/

5 9

[ruby-core:115525] [Ruby master Feature#20027] Range Deconstruction
by stuyam (Stuart Yamartino) 22 Dec '23

22 Dec '23

Issue #20027 has been reported by stuyam (Stuart Yamartino). ---------------------------------------- Feature #20027: Range Deconstruction https://bugs.ruby-lang.org/issues/20027 * Author: stuyam (Stuart Yamartino) * Status: Open * Priority: Normal ---------------------------------------- Ranges are a powerful tool in ruby. A common range I use is a date range such as `(Date.yesterday..Date.tomorrow)`. A range will often be passed around to methods because the dates hold meaning together such as a timeframe for a table filter. Often I want to grab the original values out of a range like: ```ruby timeframe = (Date.yesterday..Date.tomorrow) start_date = timeframe.begin end_date = timeframe.end #=> start_date = yesterday #=> end_date = today ``` Similar to array and hash deconstruction I thought it would be useful to support range deconstruction like this: ```ruby start_date, end_date = (Date.yesterday..Date.tomorrow) #=> start_date = yesterday #=> end_date = today ``` This would also work for endless or beginless ranges since the beginning and end are just nil in those cases: ```ruby start_date, end_day = ..Date.tomorrow #=> start_date = nil #=> end_date = tomorrow ``` You could do this now using `to_a` like: ```ruby start_date, *middle_dates, end_date = (Date.new(2000,1,1)..Date.new(2023,1,1).to_a ``` However this has unnecessary performance issues by converting the range to an array especially if the range spans a large period, `middle_dates` would hold a very large array. Also if the range resulted in an array with 2 values, `end_date` would be nil and this wouldn't actually work to get the begin and end values. I think this provides a simple interface for a common pattern of deconstructing ranges into their beginning and end values. It would be useful for ranges regardless of date ranges or other types of ranges since they are essentially tuples. Would love to know what others think about this <3 -- https://bugs.ruby-lang.org/

4 7

[ruby-core:115862] [Ruby master Feature#18915] New error class: NotImplementedYetError or scope change for NotImplementedError
by byroot (Jean Boussier) 22 Dec '23

22 Dec '23

Issue #18915 has been updated by byroot (Jean Boussier). > How about raise NoMethodError Agreed. If people want an exception that inherits from `StandardError`, then `NoMethodError` perfectly fits the bill. I still think that "you forgot to implement this abstract method" shouldn't inherit from `StandardError` though, as it risk getting handled by the application and not surface during testing, hence why `NotImplementedError` already works great for that use case regardless of what the documentation says. Amusingly Python has the same error class for that purpose exactly: https://docs.python.org/3/library/exceptions.html#NotImplementedError > exception NotImplementedError > This exception is derived from RuntimeError. In user defined base classes, abstract methods should raise this exception when they require derived classes to override the method, or while the class is being developed to indicate that the real implementation still needs to be added. ---------------------------------------- Feature #18915: New error class: NotImplementedYetError or scope change for NotImplementedError https://bugs.ruby-lang.org/issues/18915#change-105820 * Author: Quintasan (Michał Zając) * Status: Open * Priority: Normal ---------------------------------------- # Abstract Introduce `NotImplementedYetError` exception that should be used in case when the codepath has not been implemented by the developer for some reason (maybe they're designing an abstract class or are designing some sort of interface to reuse later on) OR extend the meaning of `NotImplementedError` to cover those usecases so we don't have to introduce another exception # Background `NotImplementedError` is supposed to be raised `if the underlying operating system or Ruby runtime does not support them` (https://ruby-doc.org/core-3.1.2/NotImplementedError.html) However it appears that many people are misusing this exception by raising this in a superclass from which they later inherit from. I do realize that Ruby promotes duck-typing (the default RuboCop style guide has a cop for this – https://github.com/rubocop/ruby-style-guide#duck-typing) However I have seen this being discussed numerous times: * https://github.com/rubocop/ruby-style-guide/issues/458 * http://chrisstump.online/2016/03/23/stop-abusing-notimplementederror/ * https://oleg0potapov.medium.com/ruby-notimplementederror-dont-use-it-dff1fd… * https://gitlab.com/gitlab-org/gitlab/-/issues/354314 (which I'm the author of) * https://github.com/rmosolgo/graphql-ruby/issues/2067 (here the author actually confused it with Python's `NotImplementedError`) * https://stackoverflow.com/questions/13668068/how-to-signal-not-implemented-… # Proposal Create `NotImplementedYetError` exception OR Allow raising `NotImplementedError` in cases other than OS or Ruby runtime incompatibilities # Evaluation ### Add `NotImplementedYetError` I think a new exception is a better idea than changing the usage of an existing one just because "everyone is using it". That said it would require people to refactor their code which might prevent wider adoption of the new exception. ### Change scope of `NotImplementedError` This would require the least amount of changes possible (only a documentation change) and I believe there would be no compatibility problems whatsoever. ---Files-------------------------------- not-implemented-error-docs.patch (1.57 KB) -- https://bugs.ruby-lang.org/

1 0

[ruby-core:115861] [Ruby master Feature#18915] New error class: NotImplementedYetError or scope change for NotImplementedError
by Dan0042 (Daniel DeLorme) 22 Dec '23

22 Dec '23

Issue #18915 has been updated by Dan0042 (Daniel DeLorme). How about `raise NoMethodError, "method '#{__method__}' is not implemented in #{self.class}"` ---------------------------------------- Feature #18915: New error class: NotImplementedYetError or scope change for NotImplementedError https://bugs.ruby-lang.org/issues/18915#change-105819 * Author: Quintasan (Michał Zając) * Status: Open * Priority: Normal ---------------------------------------- # Abstract Introduce `NotImplementedYetError` exception that should be used in case when the codepath has not been implemented by the developer for some reason (maybe they're designing an abstract class or are designing some sort of interface to reuse later on) OR extend the meaning of `NotImplementedError` to cover those usecases so we don't have to introduce another exception # Background `NotImplementedError` is supposed to be raised `if the underlying operating system or Ruby runtime does not support them` (https://ruby-doc.org/core-3.1.2/NotImplementedError.html) However it appears that many people are misusing this exception by raising this in a superclass from which they later inherit from. I do realize that Ruby promotes duck-typing (the default RuboCop style guide has a cop for this – https://github.com/rubocop/ruby-style-guide#duck-typing) However I have seen this being discussed numerous times: * https://github.com/rubocop/ruby-style-guide/issues/458 * http://chrisstump.online/2016/03/23/stop-abusing-notimplementederror/ * https://oleg0potapov.medium.com/ruby-notimplementederror-dont-use-it-dff1fd… * https://gitlab.com/gitlab-org/gitlab/-/issues/354314 (which I'm the author of) * https://github.com/rmosolgo/graphql-ruby/issues/2067 (here the author actually confused it with Python's `NotImplementedError`) * https://stackoverflow.com/questions/13668068/how-to-signal-not-implemented-… # Proposal Create `NotImplementedYetError` exception OR Allow raising `NotImplementedError` in cases other than OS or Ruby runtime incompatibilities # Evaluation ### Add `NotImplementedYetError` I think a new exception is a better idea than changing the usage of an existing one just because "everyone is using it". That said it would require people to refactor their code which might prevent wider adoption of the new exception. ### Change scope of `NotImplementedError` This would require the least amount of changes possible (only a documentation change) and I believe there would be no compatibility problems whatsoever. ---Files-------------------------------- not-implemented-error-docs.patch (1.57 KB) -- https://bugs.ruby-lang.org/

1 0

[ruby-core:115587] [Ruby master Misc#20038] Strings with mixed escapes not detected around interpolation
by kddnewton (Kevin Newton) 22 Dec '23

22 Dec '23

Issue #20038 has been reported by kddnewton (Kevin Newton). ---------------------------------------- Misc #20038: Strings with mixed escapes not detected around interpolation https://bugs.ruby-lang.org/issues/20038 * Author: kddnewton (Kevin Newton) * Status: Open * Priority: Normal ---------------------------------------- I'm not 100% my understanding is correct, but here's what I think is happening: When a string is being parsed, it starts out by assuming it's the same encoding as the encoding of the file. If an \x escape sequence is found that has a value >= 0x80, it locks in that encoding. Then if a \u escape sequence is found, it will raise an error if the value is >= 0x80 and say that there are mixed escape sequences. This works for: ```ruby # encoding: ascii "\xFF \u{80}" ``` The locked in encoding is recalculated on every token, however, so if you do something like: ```ruby # encoding: ascii foo = 1 "\xFF #{foo} \u{80}" ``` then the first string token (everything up to the interpolation) will be ASCII-8BIT, and everything after the interpolation will be UTF-8. This will not be marked as an error, and will instead be compiled as normal. However, as soon as it is executed, it will raise `Encoding::CompatibilityError`. Since this is statically detectable in the parser, it seems incorrect to compile it only for it to blow up later. This could be surprising for people since if it's inside an infrequently-called method, it could end up making its way into production. -- https://bugs.ruby-lang.org/

2 2

[ruby-core:115836] [Ruby master Bug#20077] modern http client
by pynix (Pynix wang) 22 Dec '23

22 Dec '23

Issue #20077 has been reported by pynix (Pynix wang). ---------------------------------------- Bug #20077: modern http client https://bugs.ruby-lang.org/issues/20077 * Author: pynix (Pynix wang) * Status: Open * Priority: Normal * Backport: 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN ---------------------------------------- net/http is very very old and hard to use. we need a well designed http client in stdlib. -- https://bugs.ruby-lang.org/

3 5

[ruby-core:115547] [Ruby master Bug#20029] coroutine/arm64/Context.S does not support PAC/BTI
by ggardet (Guillaume GARDET) 22 Dec '23

22 Dec '23

Issue #20029 has been reported by ggardet (Guillaume GARDET). ---------------------------------------- Bug #20029: coroutine/arm64/Context.S does not support PAC/BTI https://bugs.ruby-lang.org/issues/20029 * Author: ggardet (Guillaume GARDET) * Status: Open * Priority: Normal * Backport: 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN ---------------------------------------- On aarch64/arm64, when we build with `-mbranch-protection=standard` to enable Pointer Authentication (PAC) and Branch Target Identification (BTI), the final link disable them, because `coroutine/arm64/Context.S` does not support PAC and BTI. The following warning message shows the issue: ``` [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: coroutine/arm64/Context.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. ``` More information on : * PAC: https://developer.arm.com/documentation/102433/0100/Return-oriented-program… * BTI: https://developer.arm.com/documentation/102433/0100/Jump-oriented-programmi… There are also more warning displayed (with LDFLAG `-z force-bti`) which may be related to assembler file above: ``` [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccdOARjY.ltrans0.ltrans.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccdOARjY.ltrans1.ltrans.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccdOARjY.ltrans2.ltrans.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccdOARjY.ltrans3.ltrans.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccdOARjY.ltrans4.ltrans.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccdOARjY.ltrans5.ltrans.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccdOARjY.ltrans6.ltrans.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccdOARjY.ltrans7.ltrans.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccdOARjY.ltrans8.ltrans.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccdOARjY.ltrans9.ltrans.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccdOARjY.ltrans10.ltrans.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccdOARjY.ltrans11.ltrans.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccdOARjY.ltrans12.ltrans.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccdOARjY.ltrans13.ltrans.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccdOARjY.ltrans14.ltrans.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccdOARjY.ltrans15.ltrans.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccdOARjY.ltrans16.ltrans.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccdOARjY.ltrans17.ltrans.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccdOARjY.ltrans18.ltrans.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccdOARjY.ltrans19.ltrans.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccdOARjY.ltrans20.ltrans.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccdOARjY.ltrans21.ltrans.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccdOARjY.ltrans22.ltrans.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccdOARjY.ltrans23.ltrans.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccdOARjY.ltrans24.ltrans.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccdOARjY.ltrans25.ltrans.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccdOARjY.ltrans26.ltrans.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccdOARjY.ltrans27.ltrans.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccdOARjY.ltrans28.ltrans.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccdOARjY.ltrans29.ltrans.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccdOARjY.ltrans30.ltrans.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccdOARjY.ltrans31.ltrans.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccdOARjY.ltrans32.ltrans.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccdOARjY.ltrans33.ltrans.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccdOARjY.ltrans34.ltrans.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccdOARjY.ltrans35.ltrans.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccdOARjY.ltrans36.ltrans.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccdOARjY.ltrans37.ltrans.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccdOARjY.ltrans38.ltrans.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccdOARjY.ltrans39.ltrans.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccdOARjY.ltrans40.ltrans.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccdOARjY.ltrans41.ltrans.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccdOARjY.ltrans42.ltrans.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccdOARjY.ltrans43.ltrans.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccdOARjY.ltrans44.ltrans.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccdOARjY.ltrans45.ltrans.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccdOARjY.ltrans46.ltrans.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccdOARjY.ltrans47.ltrans.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccdOARjY.ltrans48.ltrans.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccdOARjY.ltrans49.ltrans.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccdOARjY.ltrans50.ltrans.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccdOARjY.ltrans51.ltrans.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccdOARjY.ltrans52.ltrans.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccdOARjY.ltrans53.ltrans.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccdOARjY.ltrans54.ltrans.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccdOARjY.ltrans55.ltrans.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccdOARjY.ltrans56.ltrans.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccdOARjY.ltrans57.ltrans.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccdOARjY.ltrans58.ltrans.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccdOARjY.ltrans59.ltrans.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccdOARjY.ltrans60.ltrans.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccdOARjY.ltrans61.ltrans.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccdOARjY.ltrans62.ltrans.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/cciywru6.debug.temp.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccYLAnEK.debug.temp.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccOMDWM2.debug.temp.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccKwSfx4.debug.temp.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/cc0UcZ79.debug.temp.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccwFEvxB.debug.temp.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccA7PZWl.debug.temp.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/cco1BWs5.debug.temp.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/cc69GwWR.debug.temp.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccQJRoGg.debug.temp.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccQxdgKL.debug.temp.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccwlSFnu.debug.temp.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccIV93Ty.debug.temp.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/cc80Z1I6.debug.temp.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccQvoKBh.debug.temp.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccF4fgVR.debug.temp.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccnZTEeL.debug.temp.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccB6xnUm.debug.temp.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/cclysC9W.debug.temp.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccdecmLz.debug.temp.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccjPDXPI.debug.temp.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccJZkU7F.debug.temp.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/cc3YUbr0.debug.temp.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccbjv5UA.debug.temp.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/cchyvXDw.debug.temp.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/cc5fXOY1.debug.temp.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccSA56NP.debug.temp.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccBC6NTp.debug.temp.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccx0LSGH.debug.temp.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccpe97Jt.debug.temp.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/cc1fcXeN.debug.temp.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccvPkzas.debug.temp.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccLVhLtG.debug.temp.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/cc1P8AOZ.debug.temp.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccHFgC67.debug.temp.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccdobe5Z.debug.temp.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/cczj5fpf.debug.temp.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccnx7HaS.debug.temp.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/cclgpgcE.debug.temp.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccFCFv3m.debug.temp.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccL90EU9.debug.temp.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccJM9ZKx.debug.temp.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/cc7E7N3b.debug.temp.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccrD7el8.debug.temp.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccDRbeGd.debug.temp.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccnz25d3.debug.temp.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccx2kRDb.debug.temp.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/cc8qpL5K.debug.temp.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccTxXwIE.debug.temp.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccyhtIpt.debug.temp.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccw06qxn.debug.temp.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccujdk33.debug.temp.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccapzdM7.debug.temp.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccyrE5Dy.debug.temp.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccK1tthq.debug.temp.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccYStpJT.debug.temp.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccoyuoLI.debug.temp.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/cca3ZE6u.debug.temp.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccmjRQkR.debug.temp.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccWhZhgr.debug.temp.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccg86XO6.debug.temp.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccEUTnCx.debug.temp.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/cccqt0zE.debug.temp.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccYsIhcV.debug.temp.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/cciZniaF.debug.temp.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/cc8PHs6I.debug.temp.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccwsJEPt.debug.temp.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/cc28q1jl.debug.temp.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccYS3JH0.debug.temp.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/cc81r5f4.debug.temp.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccWnQamA.debug.temp.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccKBgOZ8.debug.temp.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccEeEDFw.debug.temp.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/cc0Radx5.debug.temp.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccUqQpiO.debug.temp.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccGZBM2N.debug.temp.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccKrvFKD.debug.temp.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccVqBIQB.debug.temp.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccaBdhfy.debug.temp.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccuz5CcU.debug.temp.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. [ 133s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: /tmp/ccGfkAbz.debug.temp.o: warning: BTI turned on by -z force-bti when all inputs do not have BTI in NOTE section. ``` -- https://bugs.ruby-lang.org/

5 4

[ruby-core:115188] [Ruby master Bug#19977] (nil..nil) === x can raise an exception, differing from Range#cover?
by kyanagi (Kouhei Yanagita) 22 Dec '23

22 Dec '23

Issue #19977 has been reported by kyanagi (Kouhei Yanagita). ---------------------------------------- Bug #19977: (nil..nil) === x can raise an exception, differing from Range#cover? https://bugs.ruby-lang.org/issues/19977 * Author: kyanagi (Kouhei Yanagita) * Status: Open * Priority: Normal * ruby -v: ruby 3.3.0dev (2023-10-27T03:13:17Z master f9f0cfe785) [arm64-darwin22] * Backport: 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN ---------------------------------------- I investigated Range#=== and Range#cover?, and found that the only difference in behavior between them would be that `(nil..nil) === x` could throw an exception. ``` % ~/tmp/ruby-master/bin/ruby -v ruby 3.3.0dev (2023-10-27T03:13:17Z master f9f0cfe785) [arm64-darwin22] ``` ``` % ~/tmp/ruby-master/bin/ruby -e 'p (nil..nil) === "a"' -e:1:in `===': cannot determine inclusion in beginless/endless ranges (TypeError) p (nil..nil) === "a" ^^^ from -e:1:in `<main>' ``` ``` % ~/tmp/ruby-master/bin/ruby -e 'p (nil..nil).cover?("a")' true ``` Is this difference intended? According to NEWS, `Range#===` uses `cover?` since Ruby 2.6 (For `String`, since Ruby 2.7). Following this, `(nil..nil) === x` should not throw an exception in the same way as `(nil..nil).cover?(x)`. history: `(nil..nil) === "a"` throws an exception since https://github.com/ruby/ruby/commit/04a92a6. For "linear objects" (`Integer`, `Float`, `Numeric`, `Time`), it has beed fixed not to throw an exception on https://github.com/ruby/ruby/commit/fb17c83. related issues: * [Bug #15449] Range#=== is not using cover in Ruby 2.6 * [Bug #18580] Range#include? inconsistency for beginless String ranges * [Bug #19533] Behavior of ===/include? on a beginless/endless range (nil..nil) changed in ruby 3.2 -- https://bugs.ruby-lang.org/

2 5

[ruby-core:115824] [Ruby master Bug#20074] IRB/Pry search up arrow in 3.3 changed behaviour "\e[A": history-search-backward
by oleg_antonyan (Oleg Antonyan) 21 Dec '23

21 Dec '23

Issue #20074 has been reported by oleg_antonyan (Oleg Antonyan). ---------------------------------------- Bug #20074: IRB/Pry search up arrow in 3.3 changed behaviour "\e[A": history-search-backward https://bugs.ruby-lang.org/issues/20074 * Author: oleg_antonyan (Oleg Antonyan) * Status: Open * Priority: Normal * ruby -v: ruby 3.3.0rc1 (2023-12-11 master a49643340e) +YJIT [x86_64-linux] * Backport: 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN ---------------------------------------- In 3.3 since preview 1 this handy readline feature is kind of broken ``` shell $ cat ~/.inputrc "\e[A": history-search-backward "\e[B": history-search-forward ``` It supposed to search history by starting typing substring, you hit up arrow and it brings the line starting from this substring from the history. And it does that, but the problem is when you don't type anything and just hit up arrow it brings the latest history item and places the cursor at the beginning of line. Previously (up to 3.2.2) it used to put cursor at the end of the line. This is how it works pretty much everywhere (bash, for example, or in test C program that loops over `readline("> ")`), so the problem is in the way Ruby 3.3+ uses readline, but not readline itself. openSUSE Timbleweed 64bit kernel 6.6.6-1-default Ruby 3.3.0-rc1 (installed via rbenv or manually from source tarball - same behavior) libreadline 8.2 (but tried version 7 with teh same outcome) -- https://bugs.ruby-lang.org/

2 2

[ruby-core:115550] [Ruby master Bug#20031] Regexp using greedy quantifier and unions on a big string uses a lot of memory
by FabienChaynes (Fabien Chaynes) 21 Dec '23

21 Dec '23

Issue #20031 has been reported by FabienChaynes (Fabien Chaynes). ---------------------------------------- Bug #20031: Regexp using greedy quantifier and unions on a big string uses a lot of memory https://bugs.ruby-lang.org/issues/20031 * Author: FabienChaynes (Fabien Chaynes) * Status: Open * Priority: Normal * ruby -v: ruby 3.2.2 (2023-03-30 revision e51014f9c0) [x86_64-linux] * Backport: 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN ---------------------------------------- Trying to match on some regexp using a greedy quantifier on any character (`.*`) and unions (`foo|bar`) uses a lot of memory if the string we want to match on is big. # Reproduction code ```ruby puts RUBY_DESCRIPTION unless File.exist?("/tmp/fake_email.eml") content = "Accept-Language: fr-FR, en-US#{"0" * 50_000_000}" File.write("/tmp/fake_email.eml", content) end content = File.read("/tmp/fake_email.eml") def print_size(context, sike_kb) puts "#{context}: #{(sike_kb / 1024.0).round(1)} MB" end print_size("baseline", `ps ax -o pid,rss | grep -E "^[[:space:]]*#{$$}"`.strip.split.map(&:to_i).last) print_size("content", content.bytesize / 1024) REGEXP_UNION = Regexp.union( "Accept-Language:", "Thread-Topic:", ).freeze reg = /.*#{REGEXP_UNION}/ p reg GC.start print_size("before match?", `ps ax -o pid,rss | grep -E "^[[:space:]]*#{$$}"`.strip.split.map(&:to_i).last) allocated = GC.stat(:total_allocated_objects) p content.match(reg) p GC.stat(:total_allocated_objects) - allocated GC.start print_size("after match?", `ps ax -o pid,rss | grep -E "^[[:space:]]*#{$$}"`.strip.split.map(&:to_i).last) p "---" ``` Output: ```bash $ /usr/bin/time -v ruby full_repro.rb ruby 3.2.2 (2023-03-30 revision e51014f9c0) [x86_64-linux] baseline: 71.3 MB content: 47.7 MB /.*(?-mix:Accept\-Language:|Thread\-Topic:)/ before match?: 71.3 MB #<MatchData "Accept-Language:"> 14 after match?: 71.6 MB "---" Command being timed: "ruby full_repro.rb" User time (seconds): 1.15 System time (seconds): 0.74 Percent of CPU this job got: 100% Elapsed (wall clock) time (h:mm:ss or m:ss): 0:01.89 Average shared text size (kbytes): 0 Average unshared data size (kbytes): 0 Average stack size (kbytes): 0 Average total size (kbytes): 0 Maximum resident set size (kbytes): 2423108 Average resident set size (kbytes): 0 Major (requiring I/O) page faults: 0 Minor (reclaiming a frame) page faults: 609575 Voluntary context switches: 52 Involuntary context switches: 12 Swaps: 0 File system inputs: 0 File system outputs: 0 Socket messages sent: 0 Socket messages received: 0 Signals delivered: 0 Page size (bytes): 4096 Exit status: 0 ``` strace: ```bash $ sudo strace -p 588834 strace: Process 588834 attached [...] mmap(NULL, 249856, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f8e92dd3000 mremap(0x7f8e92dd3000, 249856, 495616, MREMAP_MAYMOVE) = 0x7f8e92d5a000 mremap(0x7f8e92d5a000, 495616, 987136, MREMAP_MAYMOVE) = 0x7f8e92c69000 mremap(0x7f8e92c69000, 987136, 1970176, MREMAP_MAYMOVE) = 0x7f8e92a88000 mremap(0x7f8e92a88000, 1970176, 3936256, MREMAP_MAYMOVE) = 0x7f8e926c7000 mremap(0x7f8e926c7000, 3936256, 7868416, MREMAP_MAYMOVE) = 0x7f8e91f46000 mremap(0x7f8e91f46000, 7868416, 15732736, MREMAP_MAYMOVE) = 0x7f8e91045000 mremap(0x7f8e91045000, 15732736, 31461376, MREMAP_MAYMOVE) = 0x7f8e8a8af000 mremap(0x7f8e8a8af000, 31461376, 62918656, MREMAP_MAYMOVE) = 0x7f8e86cae000 mremap(0x7f8e86cae000, 62918656, 125833216, MREMAP_MAYMOVE) = 0x7f8e7f4ad000 mremap(0x7f8e7f4ad000, 125833216, 251662336, MREMAP_MAYMOVE) = 0x7f8e704ac000 mremap(0x7f8e704ac000, 251662336, 503320576, MREMAP_MAYMOVE) = 0x7f8e524ab000 mremap(0x7f8e524ab000, 503320576, 1006637056, MREMAP_MAYMOVE) = 0x7f8e164aa000 mremap(0x7f8e164aa000, 1006637056, 2013270016, MREMAP_MAYMOVE) = 0x7f8d9e4a9000 mremap(0x7f8d9e4a9000, 2013270016, 4026535936, MREMAP_MAYMOVE) = 0x7f8cae4a8000 mmap(NULL, 12500992, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f8e92224000 munmap(0x7f8cae4a8000, 4026535936) = 0 munmap(0x7f8e92224000, 12500992) = 0 writev(1, [{iov_base="#<MatchData \"Accept-Language:\">", iov_len=31}, {iov_base="\n", iov_len=1}], 2) = 32 [...] ``` We can see that the memory retained by Ruby is low (71.6 MB), but `content.match(reg)` used 2_423_108 kbytes (~2.4 GB) in the regex engine. # Findings To reproduce we need: - a greedy quantifier on any character (`.*`) - a union with at least two members (`foo|bar`). More members won't increase the memory consumption further - to perform the match on a long string The memory seems to increase linearly against the string size: |String size |Memory consumed | |--|--| | 11.9 MB | 629_988 kbytes | | 23.8 MB | 1_235_976 kbytes | | 47.7 MB | 2_423_076 kbytes | I was able to reproduce it on old Ruby versions as well. @byroot helped me to put all this together and according to his investigation the memory allocation would be coming from `regexec.c:4100` (https://github.com/ruby/ruby/blob/85092ecd6f5c4d12d0cb1d6dfa7040337a4f558b/…) ``` size_t match_cache_buf_length = (num_match_cache_points >> 3) + (num_match_cache_points & 7 ? 1 : 0) + 1; uint8_t* match_cache_buf = (uint8_t*)xmalloc(match_cache_buf_length * sizeof(uint8_t)); ``` It seems surprising to use that much memory compared to the string size. Is it expected? -- https://bugs.ruby-lang.org/

3 3