You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@stdcxx.apache.org by "Martin Sebor (JIRA)" <ji...@apache.org> on 2008/03/25 17:51:25 UTC
[jira] Created: (STDCXX-796) [gcc 4.1.1] many -Winline warnings
[gcc 4.1.1] many -Winline warnings
----------------------------------
Key: STDCXX-796
URL: https://issues.apache.org/jira/browse/STDCXX-796
Project: C++ Standard Library
Issue Type: Bug
Components: Build
Affects Versions: 4.2.0
Environment: gcc 4.1.1
Reporter: Martin Sebor
Optimized builds with recent versions of gcc produce thousands of inlining warnings. See:
{noformat}
$ gunzip -c linux_redhat_el-5.0-em64t-gcc-4.1.1-12d-639851-log.gz | grep "inlining failed" | wc -l
4191
{noformat}
We should at least make an effort to silence those coming out of library headers (e.g., by applying {{#pragma GCC system_header}} but we might want to review them first to see if they could be used to optimize our code.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (STDCXX-796) [gcc 4.1.1] many -Winline warnings
Posted by "Martin Sebor (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/STDCXX-796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12586209#action_12586209 ]
Martin Sebor commented on STDCXX-796:
-------------------------------------
As a data point: in a 12D build of stdcxx with gcc 3.4.6 there are a total of 17,569 of these warnings. Only 121 of them are distinct (most are repeated occurrences pointing to the same piece of code), Of these 68 are in the library headers.
> [gcc 4.1.1] many -Winline warnings
> ----------------------------------
>
> Key: STDCXX-796
> URL: https://issues.apache.org/jira/browse/STDCXX-796
> Project: C++ Standard Library
> Issue Type: Bug
> Components: Build
> Affects Versions: 4.2.0
> Environment: gcc 4.1.1
> Reporter: Martin Sebor
> Fix For: 4.2.2
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> Optimized builds with recent versions of gcc produce thousands of inlining warnings. See:
> {noformat}
> $ gunzip -c linux_redhat_el-5.0-em64t-gcc-4.1.1-12d-639851-log.gz | grep "inlining failed" | wc -l
> 4191
> {noformat}
> We should at least make an effort to silence those coming out of library headers (e.g., by applying {{#pragma GCC system_header}} but we might want to review them first to see if they could be used to optimize our code.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (STDCXX-796) [gcc 4.1.1] many -Winline warnings
Posted by "Martin Sebor (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/STDCXX-796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Sebor reassigned STDCXX-796:
-----------------------------------
Assignee: Martin Sebor
> [gcc 4.1.1] many -Winline warnings
> ----------------------------------
>
> Key: STDCXX-796
> URL: https://issues.apache.org/jira/browse/STDCXX-796
> Project: C++ Standard Library
> Issue Type: Bug
> Components: Build and Installation
> Affects Versions: 4.2.0
> Environment: gcc 4.1.1
> Reporter: Martin Sebor
> Assignee: Martin Sebor
> Fix For: 4.2.2
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> Optimized builds with recent versions of gcc produce thousands of inlining warnings. See:
> {noformat}
> $ gunzip -c linux_redhat_el-5.0-em64t-gcc-4.1.1-12d-639851-log.gz | grep "inlining failed" | wc -l
> 4191
> {noformat}
> We should at least make an effort to silence those coming out of library headers (e.g., by applying {{#pragma GCC system_header}} but we might want to review them first to see if they could be used to optimize our code.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (STDCXX-796) [gcc 4.1.1] many -Winline warnings
Posted by "Martin Sebor (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/STDCXX-796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Sebor updated STDCXX-796:
--------------------------------
Fix Version/s: 4.2.2
Scheduled for 4.2.2.
> [gcc 4.1.1] many -Winline warnings
> ----------------------------------
>
> Key: STDCXX-796
> URL: https://issues.apache.org/jira/browse/STDCXX-796
> Project: C++ Standard Library
> Issue Type: Bug
> Components: Build
> Affects Versions: 4.2.0
> Environment: gcc 4.1.1
> Reporter: Martin Sebor
> Fix For: 4.2.2
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> Optimized builds with recent versions of gcc produce thousands of inlining warnings. See:
> {noformat}
> $ gunzip -c linux_redhat_el-5.0-em64t-gcc-4.1.1-12d-639851-log.gz | grep "inlining failed" | wc -l
> 4191
> {noformat}
> We should at least make an effort to silence those coming out of library headers (e.g., by applying {{#pragma GCC system_header}} but we might want to review them first to see if they could be used to optimize our code.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.