[ 
https://issues.apache.org/jira/browse/TS-4302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15225097#comment-15225097
 ] 

ASF GitHub Bot commented on TS-4302:
------------------------------------

Github user zwoop commented on the pull request:

    https://github.com/apache/trafficserver/pull/548#issuecomment-205506347
  
    @jpeach Agreed. Can you file another Jira, and ask jsime to add a section 
to this document where we document all options to configure ? That makes more 
sense than adding this new one (which is almost never going to be used). 


> Compiler warnings on OmniOS w. gcc 5.1
> --------------------------------------
>
>                 Key: TS-4302
>                 URL: https://issues.apache.org/jira/browse/TS-4302
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: Build, Core
>            Reporter: Leif Hedstrom
>            Assignee: Leif Hedstrom
>            Priority: Blocker
>             Fix For: 6.2.0
>
>
> Getting these warnings from gcc 5.1:
> {code}
> In file included from 
> /home/leif/apache/trafficserver.git/iocore/net/P_Net.h:94:0,
>                  from 
> /home/leif/apache/trafficserver.git/proxy/InkAPIInternal.h:29,
>                  from 
> /home/leif/apache/trafficserver.git/mgmt/ProcessManager.cc:28:
> /home/leif/apache/trafficserver.git/iocore/net/P_UnixNet.h: In function ‘void 
> read_disable(NetHandler*, UnixNetVConnection*)’:
> /home/leif/apache/trafficserver.git/iocore/net/P_UnixNet.h:424:30: warning: 
> overflow in implicit constant conversion [-Woverflow]
>    vc->ep.modify(-EVENTIO_READ);
>                               ^
> /home/leif/apache/trafficserver.git/iocore/net/P_UnixNet.h: In function ‘void 
> write_disable(NetHandler*, UnixNetVConnection*)’:
> /home/leif/apache/trafficserver.git/iocore/net/P_UnixNet.h:445:31: warning: 
> overflow in implicit constant conversion [-Woverflow]
>    vc->ep.modify(-EVENTIO_WRITE);
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to