This is the mail archive of the binutils@sourceware.org mailing list for the binutils 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: comparing undefined symbols with constants

From: "Jan Beulich" <JBeulich at suse dot com>
To: "Alan Modra" <amodra at gmail dot com>
Cc: <binutils at sourceware dot org>
Date: Mon, 29 Jan 2018 02:45:34 -0700
Subject: Re: comparing undefined symbols with constants
Authentication-results: sourceware.org; auth=none
References: <5A69BCD402000078001A2437@prv-mh.provo.novell.com> <20180128232918.GI20622@bubble.grove.modra.org>

>>> On 29.01.18 at 00:29, <amodra@gmail.com> wrote:
> On Thu, Jan 25, 2018 at 03:17:40AM -0700, Jan Beulich wrote:
>> as the documentation doesn't clarify this, I'd like to understand
>> whether "<undefined> == <constant>" being always false, and
>> "<undefined> != <constant>" being always true is really intended
>> to be that way.
> 
> Yes, I think so.

Interesting. This, as explained, not being correct in certain cases is
not considered a problem then? (Not that I could think of a neat way
to address this without breaking code actually relying on the current
behavior.)

Jan

Follow-Ups:
- Re: comparing undefined symbols with constants
  - From: Alan Modra

References:
- comparing undefined symbols with constants
  - From: Jan Beulich
- Re: comparing undefined symbols with constants
  - From: Alan Modra

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