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: [nvptx, committed] Disable -gstatement-frontiers for nvptx


On Dec 29, 2017, Tom de Vries <Tom_deVries@mentor.com> wrote:

> On 12/29/2017 05:12 AM, Alexandre Oliva wrote:
>> On Dec 27, 2017, Tom de Vries <Tom_deVries@mentor.com> wrote:
>> 
>>> .loc file_index line_number column_position
>> 
>>> so this causes ptxas errors when compiling something for nvptx with
>>> -g, which breaks the nvptx build.
>> 
>> What do the errors look like?

>     16  .loc 1 15 1 is_stmt 0

Oh, is_stmt is not a new assembler feature, nor is it one that's
introduced by SFN, but SFN does indeed get GCC to exercise it in cases
it didn't before, and that completely escaped me when I was surprised by
your previous email.  Thanks for the data, it clears it all up for me.

> If you point me to the location of a configure test that is supposed
> to file, I can try to find out why it passes.

Thanks, even the configure test for '.loc ... view' support is in the
LVU patch yet to be reviewed and installed.

Now, perhaps it would be wise to introduce a test for is_stmt support in
.loc directives, now that we know there are assemblers that don't
support it.

-- 
Alexandre Oliva, freedom fighter    http://FSFLA.org/~lxoliva/
You must be the change you wish to see in the world. -- Gandhi
Be Free! -- http://FSFLA.org/   FSF Latin America board member
Free Software Evangelist|Red Hat Brasil GNU Toolchain Engineer


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