Skip to content

Conversation

@DenisTarasyuk
Copy link
Contributor

@DenisTarasyuk DenisTarasyuk commented Apr 29, 2024

Rationale for this change

Fixing ascii_utf8 function that has different return result on x86 and Arm due to default char type sign difference on those platforms. Added tests to cover existing x86 behavior for ascii symbols with code >127.

What changes are included in this PR?

  1. Added type cast to signed char to save existing x86 behavior on Arm platform.
  2. Added tests cases for negative results.

Are these changes tested?

UT included.

Are there any user-facing changes?

None

@github-actions
Copy link

⚠️ GitHub issue #41433 has been automatically assigned in GitHub to PR creator.

Copy link
Member

@kou kou left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1

I think that the behavior of >=128 value is undefined because ASCII defines only 0..127. But this will not be harmful.

@kou kou merged commit 6dc6623 into apache:main Apr 30, 2024
@kou kou removed the awaiting review Awaiting review label Apr 30, 2024
@github-actions github-actions bot added the awaiting merge Awaiting merge label Apr 30, 2024
@conbench-apache-arrow
Copy link

After merging your PR, Conbench analyzed the 7 benchmarking runs that have been run so far on merge-commit 6dc6623.

There were no benchmark performance regressions. 🎉

The full Conbench report has more details. It also includes information about 23 possible false positives for unstable benchmarks that are known to sometimes produce them.

@DenisTarasyuk DenisTarasyuk deleted the GH-41433 branch April 30, 2024 13:07
DenisTarasyuk added a commit to DenisTarasyuk/arrow that referenced this pull request May 2, 2024
… result on x86 and Arm (apache#41434)

### Rationale for this change
Fixing ascii_utf8 function that has different return result on x86 and Arm due to default char type sign difference on those platforms. Added tests to cover existing x86 behavior for ascii symbols with code >127.

### What changes are included in this PR?

1. Added type cast to signed char to save existing x86 behavior on Arm platform.
2. Added tests cases for negative results.

### Are these changes tested?
UT included.

### Are there any user-facing changes?
None

* GitHub Issue: apache#41433

Authored-by: DenisTarasyuk <denis.tarasyuk@dremio.com>
Signed-off-by: Sutou Kouhei <kou@clear-code.com>
DenisTarasyuk added a commit to dremio/arrow that referenced this pull request May 3, 2024
… result on x86 and Arm (apache#41434)

### Rationale for this change
Fixing ascii_utf8 function that has different return result on x86 and Arm due to default char type sign difference on those platforms. Added tests to cover existing x86 behavior for ascii symbols with code >127.

### What changes are included in this PR?

1. Added type cast to signed char to save existing x86 behavior on Arm platform.
2. Added tests cases for negative results.

### Are these changes tested?
UT included.

### Are there any user-facing changes?
None

* GitHub Issue: apache#41433

Authored-by: DenisTarasyuk <denis.tarasyuk@dremio.com>
Signed-off-by: Sutou Kouhei <kou@clear-code.com>
vibhatha pushed a commit to vibhatha/arrow that referenced this pull request May 25, 2024
… result on x86 and Arm (apache#41434)

### Rationale for this change
Fixing ascii_utf8 function that has different return result on x86 and Arm due to default char type sign difference on those platforms. Added tests to cover existing x86 behavior for ascii symbols with code >127.

### What changes are included in this PR?

1. Added type cast to signed char to save existing x86 behavior on Arm platform.
2. Added tests cases for negative results.

### Are these changes tested?
UT included.

### Are there any user-facing changes?
None

* GitHub Issue: apache#41433

Authored-by: DenisTarasyuk <denis.tarasyuk@dremio.com>
Signed-off-by: Sutou Kouhei <kou@clear-code.com>
lriggs pushed a commit to lriggs/arrow that referenced this pull request Sep 6, 2024
… result on x86 and Arm (apache#41434)

### Rationale for this change
Fixing ascii_utf8 function that has different return result on x86 and Arm due to default char type sign difference on those platforms. Added tests to cover existing x86 behavior for ascii symbols with code >127.

### What changes are included in this PR?

1. Added type cast to signed char to save existing x86 behavior on Arm platform.
2. Added tests cases for negative results.

### Are these changes tested?
UT included.

### Are there any user-facing changes?
None

* GitHub Issue: apache#41433

Authored-by: DenisTarasyuk <denis.tarasyuk@dremio.com>
Signed-off-by: Sutou Kouhei <kou@clear-code.com>
DenisTarasyuk added a commit to DenisTarasyuk/arrow that referenced this pull request Oct 2, 2024
… result on x86 and Arm (apache#41434)

Fixing ascii_utf8 function that has different return result on x86 and Arm due to default char type sign difference on those platforms. Added tests to cover existing x86 behavior for ascii symbols with code >127.

1. Added type cast to signed char to save existing x86 behavior on Arm platform.
2. Added tests cases for negative results.

UT included.

None

* GitHub Issue: apache#41433

Authored-by: DenisTarasyuk <denis.tarasyuk@dremio.com>
Signed-off-by: Sutou Kouhei <kou@clear-code.com>
DenisTarasyuk added a commit to dremio/arrow that referenced this pull request Oct 4, 2024
… result on x86 and Arm (apache#41434)

Fixing ascii_utf8 function that has different return result on x86 and Arm due to default char type sign difference on those platforms. Added tests to cover existing x86 behavior for ascii symbols with code >127.

1. Added type cast to signed char to save existing x86 behavior on Arm platform.
2. Added tests cases for negative results.

UT included.

None

* GitHub Issue: apache#41433

Authored-by: DenisTarasyuk <denis.tarasyuk@dremio.com>
Signed-off-by: Sutou Kouhei <kou@clear-code.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants