[#101981] [Ruby master Bug#17519] set_visibility fails when a prepended module and a refinement both exist — dbfeldman@...

Issue #17519 has been reported by fledman (David Feldman).

12 messages 2021/01/08

[#102003] [Ruby master Bug#17527] rb_io_wait_readable/writable with scheduler don't check errno — julien@...

Issue #17527 has been reported by ysbaddaden (Julien Portalier).

13 messages 2021/01/11

[#102065] [Ruby master Bug#17536] Segfault in `CFUNC :define_method` — v.ondruch@...

Issue #17536 has been reported by vo.x (Vit Ondruch).

13 messages 2021/01/13

[#102083] [Ruby master Bug#17540] A segfault due to Clang/LLVM optimization on 32-bit ARM Linux — xtkoba+ruby@...

Issue #17540 has been reported by xtkoba (Tee KOBAYASHI).

12 messages 2021/01/14

[#102102] [Ruby master Bug#17543] Ractor isolation broken by `self` in shareable proc — marcandre-ruby-core@...

Issue #17543 has been reported by marcandre (Marc-Andre Lafortune).

14 messages 2021/01/15

[#102118] [Ruby master Feature#17548] Need simple way to include symlink directories in Dir.glob — keithrbennett@...

Issue #17548 has been reported by keithrbennett (Keith Bennett).

8 messages 2021/01/17

[#102158] [Ruby master Bug#17560] Does `Module#ruby2_keywords` return `nil` or `self`? — nobu@...

Issue #17560 has been reported by nobu (Nobuyoshi Nakada).

9 messages 2021/01/19

[#102163] [Ruby master Bug#17561] The timeout option for Addrinfo.getaddrinfo is not reliable on Ruby 2.7.2 — sean@...

Issue #17561 has been reported by smcgivern (Sean McGivern).

8 messages 2021/01/19

[#102249] [Ruby master Bug#17583] Segfault on large stack(RUBY_THREAD_VM_STACK_SIZE) — yoshiokatsuneo@...

Issue #17583 has been reported by yoshiokatsuneo (Tsuneo Yoshioka).

12 messages 2021/01/26

[#102256] [Ruby master Bug#17585] DWAR5 support? — v.ondruch@...

Issue #17585 has been reported by vo.x (Vit Ondruch).

19 messages 2021/01/26

[#102301] [Ruby master Bug#17591] Test frameworks and REPLs do not show deprecation warnings by default — eregontp@...

Issue #17591 has been reported by Eregon (Benoit Daloze).

14 messages 2021/01/29

[#102305] [Ruby master Feature#17592] Ractor should allowing reading shareable class instance variables — marcandre-ruby-core@...

Issue #17592 has been reported by marcandre (Marc-Andre Lafortune).

25 messages 2021/01/29

[ruby-core:102271] [Ruby master Bug#16930] Excessive deprecation warnings for c++ compile units

From: shyouhei@...
Date: 2021-01-28 05:08:27 UTC
List: ruby-core #102271
Issue #16930 has been updated by shyouhei (Shyouhei Urabe).

Status changed from Third Party's Issue to Closed

commit:06321ea26c186434e5b943a6739ffd6bd1eb06d9 is a workaround.  To trigger our backporting process I change the status to Closed.

----------------------------------------
Bug #16930: Excessive deprecation warnings for c++ compile units
https://bugs.ruby-lang.org/issues/16930#change-90125

* Author: anatolik (Anatol Pomozov)
* Status: Closed
* Priority: Normal
* ruby -v: 2.7.1
* Backport: 2.5: UNKNOWN, 2.6: UNKNOWN, 2.7: UNKNOWN
----------------------------------------
I am using Arch Linux with the latest Ruby 2.7.1.

I am compiling a simple C++ program like this

``` cpp
#include <ruby.h>

int main() {
    return 0;
}
```

And then compile as `g++ -c main.cxx -I/usr/include/ruby-2.7.0 -I/usr/include/ruby-2.7.0/x86_64-linux`.

I see a lot of warnings are printed to the user:

```
/usr/include/ruby-2.7.0/ruby/backward/cxxanyargs.hpp:222:1: note: declared here
  222 | rb_rescue2(type *q, VALUE w, type *e, VALUE r, ...)
      | ^~~~~~~~~~
/usr/include/ruby-2.7.0/ruby/backward/cxxanyargs.hpp: In function ‘VALUE ruby::backward::cxxanyargs::rb_ensure(VALUE (*)(...), VALUE, VALUE (*)(...), VALUE)’:
/usr/include/ruby-2.7.0/ruby/backward/cxxanyargs.hpp:251:14: warning: ‘VALUE ruby::backward::cxxanyargs::rb_ensure(VALUE (*)(...), VALUE, VALUE (*)(...), VALUE)’ is deprecated: Use of ANYARGS in this function is deprecated [-Wdeprecated-declarations]
  251 |     func1_t *t = reinterpret_cast<func1_t*>(q);
      |              ^
/usr/include/ruby-2.7.0/ruby/backward/cxxanyargs.hpp:248:1: note: declared here
  248 | rb_ensure(type *q, VALUE w, type *e, VALUE r)
      | ^~~~~~~~~
/usr/include/ruby-2.7.0/ruby/backward/cxxanyargs.hpp:251:42: warning: ‘VALUE ruby::backward::cxxanyargs::rb_ensure(VALUE (*)(...), VALUE, VALUE (*)(...), VALUE)’ is deprecated: Use of ANYARGS in this function is deprecated [-Wdeprecated-declarations]
  251 |     func1_t *t = reinterpret_cast<func1_t*>(q);
      |                                          ^
/usr/include/ruby-2.7.0/ruby/backward/cxxanyargs.hpp:248:1: note: declared here
  248 | rb_ensure(type *q, VALUE w, type *e, VALUE r)
      | ^~~~~~~~~
/usr/include/ruby-2.7.0/ruby/backward/cxxanyargs.hpp:252:14: warning: ‘VALUE ruby::backward::cxxanyargs::rb_ensure(VALUE (*)(...), VALUE, VALUE (*)(...), VALUE)’ is deprecated: Use of ANYARGS in this function is deprecated [-Wdeprecated-declarations]
  252 |     func1_t *y = reinterpret_cast<func1_t*>(e);
      |              ^
/usr/include/ruby-2.7.0/ruby/backward/cxxanyargs.hpp:248:1: note: declared here
  248 | rb_ensure(type *q, VALUE w, type *e, VALUE r)
      | ^~~~~~~~~
/usr/include/ruby-2.7.0/ruby/backward/cxxanyargs.hpp:252:42: warning: ‘VALUE ruby::backward::cxxanyargs::rb_ensure(VALUE (*)(...), VALUE, VALUE (*)(...), VALUE)’ is deprecated: Use of ANYARGS in this function is deprecated [-Wdeprecated-declarations]
  252 |     func1_t *y = reinterpret_cast<func1_t*>(e);
      |                                          ^
/usr/include/ruby-2.7.0/ruby/backward/cxxanyargs.hpp:248:1: note: declared here
  248 | rb_ensure(type *q, VALUE w, type *e, VALUE r)
      | ^~~~~~~~~
/usr/include/ruby-2.7.0/ruby/backward/cxxanyargs.hpp: In function ‘VALUE ruby::backward::cxxanyargs::rb_thread_create(VALUE (*)(...), void*)’:
/usr/include/ruby-2.7.0/ruby/backward/cxxanyargs.hpp:343:12: warning: ‘VALUE ruby::backward::cxxanyargs::rb_thread_create(VALUE (*)(...), void*)’ is deprecated: Use of ANYARGS in this function is deprecated [-Wdeprecated-declarations]
  343 |     ptr_t *e = reinterpret_cast<ptr_t*>(q);
      |            ^
/usr/include/ruby-2.7.0/ruby/backward/cxxanyargs.hpp:340:1: note: declared here
  340 | rb_thread_create(type *q, void *w)
      | ^~~~~~~~~~~~~~~~
/usr/include/ruby-2.7.0/ruby/backward/cxxanyargs.hpp:343:38: warning: ‘VALUE ruby::backward::cxxanyargs::rb_thread_create(VALUE (*)(...), void*)’ is deprecated: Use of ANYARGS in this function is deprecated [-Wdeprecated-declarations]
  343 |     ptr_t *e = reinterpret_cast<ptr_t*>(q);
      |                                      ^
/usr/include/ruby-2.7.0/ruby/backward/cxxanyargs.hpp:340:1: note: declared here
  340 | rb_thread_create(type *q, void *w)
      | ^~~~~~~~~~~~~~~~
```

These warnings are coming include/ruby/backward/cxxanyargs.hpp where 
 RUBY_CXX_DEPRECATED("Use of ANYARGS in this function is deprecated") are included across the file. These deprecation warnings are printed only because the backward compatibility file is included. But there seems no way to disable backward compatibility inclusion.

These warnings should be printed only when the deprecated code is used by the user. Otherwise the compiler should be silent.



-- 
https://bugs.ruby-lang.org/

Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>

In This Thread