This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [PATCH] Fix strict-aliasing warning in resolv/res_hconf.c

From: Paul Eggert <eggert at cs dot ucla dot edu>
To: Roland McGrath <roland at hack dot frob dot com>, sellcey at imgtec dot com
Cc: libc-alpha at sourceware dot org
Date: Tue, 19 May 2015 18:03:16 -0700
Subject: Re: [PATCH] Fix strict-aliasing warning in resolv/res_hconf.c
Authentication-results: sourceware.org; auth=none
References: <5bfa6373-3817-4d31-a5ee-a8676e79b723 at BAMAIL02 dot ba dot imgtec dot org> <555BB55E dot 3050304 at cs dot ucla dot edu> <1432075989 dot 16668 dot 62 dot camel at ubuntu-sellcey> <555BC19B dot 90001 at cs dot ucla dot edu> <1432077972 dot 16668 dot 65 dot camel at ubuntu-sellcey> <20150519235817 dot 9516F2C3A73 at topped-with-meat dot com>

Roland McGrath wrote:

We need
to come up with an idiom or helper code to facilitate using it in whatever
fashion is closest to compliant and is in fact thoroughly safe.  Maybe Paul
has some ideas.

How about __attribute__((__may_alias__))? In general it's better to avoid thatattribute, but this may be one of the places where it's unavoidable.

References:
- [PATCH] Fix strict-aliasing warning in resolv/res_hconf.c
  - From: Steve Ellcey
- Re: [PATCH] Fix strict-aliasing warning in resolv/res_hconf.c
  - From: Paul Eggert
- Re: [PATCH] Fix strict-aliasing warning in resolv/res_hconf.c
  - From: Steve Ellcey
- Re: [PATCH] Fix strict-aliasing warning in resolv/res_hconf.c
  - From: Paul Eggert
- Re: [PATCH] Fix strict-aliasing warning in resolv/res_hconf.c
  - From: Steve Ellcey
- Re: [PATCH] Fix strict-aliasing warning in resolv/res_hconf.c
  - From: Roland McGrath

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]