-
Notifications
You must be signed in to change notification settings - Fork 542
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
locale.c: New build-time warnings when built with clang14 #21288
Comments
On 7/24/23 19:13, James E Keenan wrote:
Tonight for the first time in several months I configured and built a
perl on FreeBSD-12 for the purpose of detecting build-time warnings. I
build with a commit from recent days (post-5.37.1) and compiled with
|clang14|.
|$ clang14 --version clang version 14.0.6 Target:
x86_64-portbld-freebsd12.3 Thread model: posix InstalledDir:
/usr/local/llvm14/bin $ sh ./Configure -des -Dusedevel -Duseithreads
-Dcc=clang14 && \ make test_prep $ parse-build-warnings
d920333.freebsd.threaded.clang14.maketp.output.txt.gz File:
d920333.freebsd.threaded.clang14.maketp.output.txt.gz [ { char => 48,
group => "Wunused-parameter", line => 408, source => "locale.c", text =>
"unused parameter 'caller_line'", }, { char => 21, group =>
"Wunused-const-variable", line => 313, source => "locale.c", text =>
"unused variable 'category_name_lengths'", }, ... ] |
Future commits in the pipeline will remove these.
… (There were also 4 previously observed build-time warnings from
|cpan/*Compress*| modules.)
In the output of |make test_prep| I saw:
|clang14 -c -DPERL_CORE -DHAS_FPSETMASK -DHAS_FLOATINGPOINT_H
-fno-strict-aliasing -pipe -fstack-protector-strong -I/usr/local/include
-std=c99 -O2 -Wall -Werror=pointer-arith -Werror=vla -Wextra
-Wno-long-long -Wno-declaration-after-statement -Wc++-compat
-Wwrite-strings locale.c locale.c:408:48: warning: unused parameter
'caller_line' [-Wunused-parameter] const line_t caller_line) ^
locale.c:313:21: warning: unused variable 'category_name_lengths'
[-Wunused-const-variable] STATIC const Size_t category_name_lengths[] =
{ ^ 2 warnings generated. |
For line 313 in |locale.c|:
|commit a63ba98 Author: Karl Williamson
***@***.***> AuthorDate: Thu Jul 20 20:35:00 2023 -0600 Commit: Karl
Williamson ***@***.***> CommitDate: Mon Jul 24 04:10:34 2023 -0600
locale.c: Avoid runtime strlen() calls |
For line 408 in |locale.c|:
|commit a2d04a5 Author: Karl Williamson
***@***.***> AuthorDate: Thu Apr 20 15:19:50 2023 -0600 Commit: Karl
Williamson ***@***.***> CommitDate: Mon Jul 24 04:10:34 2023 -0600
locale.c: Refactor S_get_category_index() |
@khwilliamson <https://github.com/khwilliamson>, can you take a look?
Thank you very much.
Jim Keenan
—
Reply to this email directly, view it on GitHub
<#21288>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAA2DH4YDG2KY2HMLU6VCWDXR4MTNANCNFSM6AAAAAA2WKTIFI>.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
They appear to have been removed, but now we have an
... which probably comes from:
I'll proceed on the assumption that we'll soon be actually using |
I stumbled across the Issue appears to be use of an old |
Paul, thanks for keeping an eye out for this! |
The
So the only clang-specific build-time warnings still being tracked in this ticket are those mentioned in the discussion with @pmqs above. |
I'm on it now. The version of Problem is upgrading Will temporarily disable failing tests in 5.6 for now to get this checked in. I just love a rabbit-hole! |
The clang warnings are also an issue with |
This GH issue was originally focused on warnings being emitted during compilation of |
Tonight for the first time in several months I configured and built a perl on FreeBSD-12 for the purpose of detecting build-time warnings. I build with a commit from recent days (post-5.37.1) and compiled with
clang14
.(There were also 4 previously observed build-time warnings from
cpan/*Compress*
modules.)In the output of
make test_prep
I saw:For line 313 in
locale.c
:For line 408 in
locale.c
:@khwilliamson, can you take a look?
Thank you very much.
Jim Keenan
The text was updated successfully, but these errors were encountered: