Bug 1306966 - nsca: Type pun (strict-aliasing) warning seen in x86_64 build log
Summary: nsca: Type pun (strict-aliasing) warning seen in x86_64 build log
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: gluster-nagios-addons
Version: rhgs-3.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Sahina Bose
QA Contact: Sweta Anandpara
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-12 10:15 UTC by Shruti Sampat
Modified: 2018-01-30 11:48 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-01-30 11:48:03 UTC
Embargoed:


Attachments (Terms of Use)

Description Shruti Sampat 2016-02-12 10:15:39 UTC
Description of problem:
------------------------

Build Log 	Type pun (strict-aliasing) warning seen in x86_64 build log:
    287  ./nrpe.c: In function 'wait_for_connections':
    288  ./nrpe.c:1038: warning: dereferencing pointer 'nptr' does break strict-aliasing rules
    288  ./nrpe.c:1038: warning: dereferencing pointer 'nptr' does break strict-aliasing rules
    289  ./nrpe.c:1049: warning: dereferencing pointer 'nptr' does break strict-aliasing rules
    289  ./nrpe.c:1049: warning: dereferencing pointer 'nptr' does break strict-aliasing rules
    290  ./nrpe.c:1043: warning: dereferencing pointer 'nptr' does break strict-aliasing rules
    290  ./nrpe.c:1043: warning: dereferencing pointer 'nptr' does break strict-aliasing rules
    291  ./nrpe.c:1036: warning: dereferencing pointer 'nptr' does break strict-aliasing rules
    292  ./nrpe.c:1032: note: initialized from here
    293  ./nrpe.c:1078: warning: dereferencing pointer 'nptr6' does break strict-aliasing rules

Version-Release number of selected component (if applicable):
--------------------------------------------------------------
nsca-2.9.1-4.1.el6rhs

Comment 8 Sahina Bose 2018-01-30 11:48:03 UTC
Thank you for your bug report. However, this bug is being closed as it's on a component where no further new development is being undertaken.


Note You need to log in before you can comment on or make changes to this bug.