Date: Tue, 05 Mar 2013 15:57:30 +0100 From: Dimitry Andric <dim@FreeBSD.org> To: Andriy Gapon <avg@FreeBSD.org> Cc: freebsd-hackers@FreeBSD.org Subject: Re: clang generated code sometimes confuses fbt Message-ID: <513607DA.60901@FreeBSD.org> In-Reply-To: <5135DEF0.2060802@FreeBSD.org> References: <5132387E.8010808@FreeBSD.org> <51323C62.4040506@FreeBSD.org> <51325FB3.7080300@FreeBSD.org> <51337018.30000@FreeBSD.org> <51337C27.7000105@FreeBSD.org> <5133AC3B.5040504@FreeBSD.org> <51348A6A.3070606@FreeBSD.org> <5135DEF0.2060802@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2013-03-05 13:02, Andriy Gapon wrote: > on 04/03/2013 13:50 Dimitry Andric said the following: >> Actually, that way of fixing breaks it for gcc, so it should really be >> fixed in sort_iidescs() instead. See attached diff; I verified it works >> for both gcc-compiled and clang-compiled objects. > > Impossible! It looks like the attached diff was a nop change :-) > > BTW, so changing clang to match gcc is not an option? > I do not insist, just curious. I could not find a good argument to present to upstream to change this behaviour, except "gcc has been doing it for x years, without a good reason". :-) And I did not want to make yet another FreeBSD specific change. In my opinion, gcc is losing information here, e.g. the original pathname to the source file. There is no reason debugging tools cannot be fixed to be able to cope with this.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?513607DA.60901>