Skip to content

Conversation

@XuNeo
Copy link
Contributor

@XuNeo XuNeo commented Oct 11, 2024

Note: Please adhere to Contributing Guidelines.

Summary

Remove not needed warning suppression.

Since there's no warning presents now.

Impact

No impact, CI check will confirm if there's warnings.

Testing

Tested with internal CI and reports no warnings.

Since there's no warning presents now.

Signed-off-by: xuxingliang <xuxingliang@xiaomi.com>
@github-actions github-actions bot added Area: OS Components OS Components issues Size: XS The size of the change in this PR is very small labels Oct 11, 2024
@fjpanag
Copy link
Contributor

fjpanag commented Oct 11, 2024

What's wrong with keeping the warning enabled? It may be useful in the future.

@xiaoxiang781216
Copy link
Contributor

What's wrong with keeping the warning enabled? It may be useful in the future.

why? it is always good to clear the warning as much as possible.

@XuNeo
Copy link
Contributor Author

XuNeo commented Oct 11, 2024

What's wrong with keeping the warning enabled? It may be useful in the future.

Hi, This PR does exactly keep warning enabled, instead of suppress those warnings.

@xiaoxiang781216
Copy link
Contributor

let's ignore macOS ci temp break.

@xiaoxiang781216 xiaoxiang781216 merged commit b9adff0 into apache:master Oct 11, 2024
@fjpanag
Copy link
Contributor

fjpanag commented Oct 11, 2024

What's wrong with keeping the warning enabled? It may be useful in the future.

Hi, This PR does exactly keep warning enabled, instead of suppress those warnings.

Sorry, read it quickly and confused that it does the opposite.

@XuNeo XuNeo deleted the libm-newlib-remove-cflags branch October 12, 2024 05:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Area: OS Components OS Components issues Size: XS The size of the change in this PR is very small

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants