Skip to content

Conversation

@nobu
Copy link
Member

@nobu nobu commented Jun 25, 2020

No description provided.

mame and others added 3 commits June 25, 2020 16:51
Ragel generates a code `0 <= (*p)` where `*p` is char.
As char is unsigned by default on arm and RISC-V, it is warned by gcc:

```
compiling parser.c
parser.c: In function ‘JSON_parse_string’:
parser.c:1566:2: warning: comparison is always true due to limited range of data type [-Wtype-limits]
  if ( 0 <= (*p) && (*p) <= 31 )
  ^
parser.c:1596:2: warning: comparison is always true due to limited range of data type [-Wtype-limits]
  if ( 0 <= (*p) && (*p) <= 31 )
  ^
```

This change removes the warning by substituting the condition with
`0 <= (signed char)(*p)`.

ruby/ruby@8bd27c5
As it is ignored and set at building packages automatically, it is
just nonsense to set in gemspec file for input.

ruby/ruby@9a78e24
@hsbt hsbt merged commit ee70abf into ruby:master Jun 25, 2020
@hsbt
Copy link
Member

hsbt commented Jun 25, 2020

Thanks!

@voxik
Copy link

voxik commented Jun 25, 2020

Since the .gemspec is autogenerated by Rake, does the change from 9c29ce3 survive next rake gemspec run? I don't think so (have not tested myself).

@marcandre
Copy link
Member

@voxik Currently json_pure.gemspec is generated and not json.gemspec, so this is fine.

@nobu nobu deleted the sync-ruby branch July 18, 2023 07:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants