This is the mail archive of the gcc-patches@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: [PATCH] nvptx: do not implicitly enable -ftoplevel-reorder

From: Bernd Schmidt <bschmidt at redhat dot com>
To: Joseph Myers <joseph at codesourcery dot com>
Cc: Alexander Monakov <amonakov at ispras dot ru>, Thomas Schwinge <thomas at codesourcery dot com>, Nathan Sidwell <nathan at codesourcery dot com>, gcc-patches <gcc-patches at gcc dot gnu dot org>
Date: Mon, 1 Aug 2016 22:51:59 +0200
Subject: Re: [PATCH] nvptx: do not implicitly enable -ftoplevel-reorder
Authentication-results: sourceware.org; auth=none
References: <alpine.LNX.2.20.13.1607192119340.2179@monopod.intra.ispras.ru> <3aa3c3aa-2174-e6da-4a38-cd8327d2b199@acm.org> <871t2mdib9.fsf@kepler.schwinge.homeip.net> <alpine.LNX.2.20.13.1607221608140.13668@monopod.intra.ispras.ru> <ad11c79d-d7f2-4920-3885-7becd8a97ee7@redhat.com> <alpine.DEB.2.20.1608012042400.15168@digraph.polyomino.org.uk>

On 08/01/2016 10:44 PM, Joseph Myers wrote:

On Fri, 22 Jul 2016, Bernd Schmidt wrote:

What's the motivation for supporting -fno-toplevel-reorder anyway? That's
practically just a legacy mode as far as I know.


It's for code that uses toplevel asms in ways for which it matters where
they appear in relation to functions in the .s file, or otherwise uses
asms or has a build system that manipulates the .s file in ways that break
with reordering.

Yes, but that sort of thing tends not to work with nvptx anyway, so Istill don't really see the point.



Bernd

References:
- Re: [PATCH] nvptx: do not implicitly enable -ftoplevel-reorder
  - From: Joseph Myers

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