Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionThomas Sondergaard
2011-05-08 20:32:40 UTC
Created attachment 497678[details]
Small example that demonstrates the problem
Description of problem:
Version-Release number of selected component (if applicable):
g++ (GCC) 4.4.4 20100726 (Red Hat 4.4.4-13)
How reproducible:
Everytime. Compile attached sample
Steps to Reproduce:
1. g++ -I /path/to/boost_1_46_1 -g -O2 -Wall -c tst.cc
Actual results:
/home/ts/pack/boost_1_46_1/boost/optional/optional.hpp: In function ‘std::vector<B, std::allocator<B> > f()’:
/home/ts/pack/boost_1_46_1/boost/optional/optional.hpp:346: warning: dereferencing pointer ‘pretmp.811’ does break strict-aliasing rules
cc1plus: note: initialized from here
/home/ts/pack/boost_1_46_1/boost/optional/optional.hpp:346: warning: dereferencing pointer ‘pretmp.811’ does break strict-aliasing rules
cc1plus: note: initialized from here
/home/ts/pack/boost_1_46_1/boost/optional/optional.hpp:346: warning: dereferencing pointer ‘pretmp.811’ does break strict-aliasing rules
cc1plus: note: initialized from here
/home/ts/pack/boost_1_46_1/boost/optional/optional.hpp:346: warning: dereferencing pointer ‘pretmp.811’ does break strict-aliasing rules
cc1plus: note: initialized from here
/home/ts/pack/boost_1_46_1/boost/optional/optional.hpp:346: warning: dereferencing pointer ‘pretmp.811’ does break strict-aliasing rules
cc1plus: note: initialized from here
Expected results:
No warnings
Additional info:
Modifying the example a little bit in ways that seem irrelevant makes the problem go away. Found in real-use code which was subsequently reduced to the attached sample.
Comment 2RHEL Program Management
2011-05-09 06:00:12 UTC
Since RHEL 6.1 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.
Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.
Comment 3Thomas Sondergaard
2011-05-09 21:02:59 UTC
(In reply to comment #2)
> Since RHEL 6.1 External Beta has begun, and this bug remains
> unresolved, it has been rejected as it is not proposed as
> exception or blocker.
Puzzling message. Rejected altogether or for 6.1? Should I file it upstream, ie gcc's own bugzilla?
Please provide preprocessed source (g++ -O2 -I /path/to/boost_1_46_1 -E -o tst.ii tst.cc and attach tst.ii), I certainly can't reproduce it with boost 1.44.
Comment 5Thomas Sondergaard
2011-05-10 19:56:45 UTC
Created attachment 498142[details]
Preprocessor output
Generated with the following command line as requested in comment #4
g++ -O2 -I /home/ts/pack/boost_1_46_1z -E -o tst.iix tst.cc
Comment 7RHEL Program Management
2011-06-15 13:25:08 UTC
Development Management has reviewed and declined this request. You may appeal
this decision by reopening this request.
Created attachment 497678 [details] Small example that demonstrates the problem Description of problem: Version-Release number of selected component (if applicable): g++ (GCC) 4.4.4 20100726 (Red Hat 4.4.4-13) How reproducible: Everytime. Compile attached sample Steps to Reproduce: 1. g++ -I /path/to/boost_1_46_1 -g -O2 -Wall -c tst.cc Actual results: /home/ts/pack/boost_1_46_1/boost/optional/optional.hpp: In function ‘std::vector<B, std::allocator<B> > f()’: /home/ts/pack/boost_1_46_1/boost/optional/optional.hpp:346: warning: dereferencing pointer ‘pretmp.811’ does break strict-aliasing rules cc1plus: note: initialized from here /home/ts/pack/boost_1_46_1/boost/optional/optional.hpp:346: warning: dereferencing pointer ‘pretmp.811’ does break strict-aliasing rules cc1plus: note: initialized from here /home/ts/pack/boost_1_46_1/boost/optional/optional.hpp:346: warning: dereferencing pointer ‘pretmp.811’ does break strict-aliasing rules cc1plus: note: initialized from here /home/ts/pack/boost_1_46_1/boost/optional/optional.hpp:346: warning: dereferencing pointer ‘pretmp.811’ does break strict-aliasing rules cc1plus: note: initialized from here /home/ts/pack/boost_1_46_1/boost/optional/optional.hpp:346: warning: dereferencing pointer ‘pretmp.811’ does break strict-aliasing rules cc1plus: note: initialized from here Expected results: No warnings Additional info: Modifying the example a little bit in ways that seem irrelevant makes the problem go away. Found in real-use code which was subsequently reduced to the attached sample.