-
Notifications
You must be signed in to change notification settings - Fork 192
[JENKINS-73509] GCC parser does not handle cc1/cc1plus warnings #1253
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
base: main
Are you sure you want to change the base?
Conversation
In member function 'void CInput::UpdateText(int, int, int)': | ||
cc1plus: warning: 'void* _builtin_memset(void*, int, long unsigned int)': specified size 18446744073709551612 | ||
exceeds maximum object size 9223372036854775807 [-Wstringop-overflow=] | ||
|
||
In member function 'void CInput::UpdateText(int, int, int)': | ||
cc1: warning: 'void* _builtin_memcpy(void*, const void*, long unsigned int)': specified size 18446744073709551612 | ||
exceeds maximum object size 9223372036854775807 [-Wstringop-overflow=] | ||
|
||
testhist.l:451: warning: `void yyunput(int, char*)' defined but not used |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this output generated by an actual compiler call? Or did you just copy the text from the issue?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
As it was there in JIRA, I didn't validate it against raw compiler logs.
Please let me know if there’s anything I need to update or improve to help move it forward.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Without more details and input from the author of the issue it does not make sense to continue here.
private static final String GCC_WARNING_PATTERN = "^(?:\\s*(?:\\[.*\\]\\s*)?([^ ]*\\.[chpimxsola0-9]+):(?:(\\d*):" | ||
+ "(?:\\d*:)*\\s*(?:(warning|error|note)\\s*:|\\s*(.*))|\\s*(undefined reference to.*))(.*)|.*ld:\\s*(.*-l(" | ||
+ ".*)))$"; | ||
+ ".*))|(?:In .+?:\\s*)?(cc1(?:plus)?):\\s*(warning|error|note):\\s*(.*))$"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm, this makes the parser more complex. Do you know if there are several different messages not picked up currently? I asked in JENKINS-73509, but maybe you have an answer already.
d95815f
to
569f920
Compare
JENKINS-73509
GCC parser does not handle cc1/cc1plus warnings
Testing done
Submitter checklist