This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC 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: Another weird CPP result

From: Neil Booth <neil at daikokuya dot co dot uk>
To: Zack Weinberg <zack at codesourcery dot com>
Cc: Jason R Thorpe <thorpej at wasabisystems dot com>, gcc-bugs at gcc dot gnu dot org
Date: Tue, 16 Jul 2002 07:51:16 +0100
Subject: Re: Another weird CPP result
References: <20020716024341.3B1E17DA4@yeah-baby.shagadelic.org> <20020715204007.A13737@dr-evil.shagadelic.org> <20020716062917.GA29448@daikokuya.co.uk> <20020716064832.GC358@codesourcery.com>

Zack Weinberg wrote:-

> I just haven't gotten around to it.  It should get done for 3.3.  Does
> it need to be fixed for 3.1.1?  If so I'll bump it up the list.

I don't think so.  3.3 is fine.

> > I'm still not clear how this solves the problem in general, since
> > different paths can refer to the same file.  Under UNIX we can check
> > dev/inode pairs, but I'm not aware of a proper portable solution.
> 
> You are imagining a situation where, for instance, the -M file and the
> normal output are hard or symbolic links to the same inode?  The user
> must have done that deliberately; I'm fine with saying that that's not
> supported.

I think I'm just confused, and the problem is not as hard as I think it
is.

Neil.

References:
- Another weird CPP result
  - From: Jason R Thorpe
- Re: Another weird CPP result
  - From: Neil Booth
- Re: Another weird CPP result
  - From: Zack Weinberg

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