All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yu, Mingli" <mingli.yu@windriver.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>,
	Khem Raj <raj.khem@gmail.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] boost: Improve reproducibility
Date: Fri, 15 Jun 2018 15:31:40 +0800	[thread overview]
Message-ID: <5B236B5C.7060603@windriver.com> (raw)
In-Reply-To: <CANNYZj-pDd=Dpgs4sk-73HbxXFKa_aBLMJaRYSxzvdq-EO6aKg@mail.gmail.com>



On 2018年06月15日 14:54, Alexander Kanavin wrote:
> Thanks! Mingli, can you try this please?

Sure,

>
> Alex
>
> 2018-06-15 9:44 GMT+03:00 Khem Raj <raj.khem@gmail.com>:
>>
>>
>> On 6/1/18 12:34 PM, Alexander Kanavin wrote:
>>>
>>> On 06/01/2018 09:33 PM, Khem Raj wrote:
>>>>>
>>>>> The .s file is not generated and it does not contain any .file
>>>>> directives. The .o file also does not contain the path. It appears in
>>>>> the final .so library at linking stage.
>>>>
>>>>
>>>> Can you share the linker cmdline ?
>>>
>>>
>>> https://pastebin.com/WK9GVDfj
>>>
>>> Note that of the three assembly-generated object files, only the path to
>>> the first shows up in the .so - because of assembly labels I believe.
>>>
>>
>> Thanks for sharing this. If there is a no file directive in an object file
>> then linker will use whatever is specified on linker cmdline so thats what
>> we see, We should define FILE symbol explicitly for .S files here, for C/C++
>> files compiler does that automatically.
>>
>> Other files dont make a claim in final symbol table since this one file
>> alone has cross referencing to symbols from other objects.
>>
>> Something like this will help

Thanks Khem very much!

Have set .file section in .S file as you suggested, it works.

Thanks,

>>
>> Index: boost_1_67_0/libs/context/src/asm/make_i386_sysv_elf_gas.S
>> ===================================================================
>> --- boost_1_67_0.orig/libs/context/src/asm/make_i386_sysv_elf_gas.S
>> +++ boost_1_67_0/libs/context/src/asm/make_i386_sysv_elf_gas.S
>> @@ -23,7 +23,7 @@
>>    *
>> ----------------------------------------------------------------------------------
>> *
>>    *                  *
>>
>> ****************************************************************************************/
>> -
>> +.file "make_i386_sysv_elf_gas.S"
>>   .text
>>   .globl make_fcontext
>>   .align 2
>> Index: boost_1_67_0/libs/context/src/asm/make_x86_64_sysv_elf_gas.S
>> ===================================================================
>> --- boost_1_67_0.orig/libs/context/src/asm/make_x86_64_sysv_elf_gas.S
>> +++ boost_1_67_0/libs/context/src/asm/make_x86_64_sysv_elf_gas.S
>> @@ -23,7 +23,7 @@
>>    *
>> ----------------------------------------------------------------------------------
>> *
>>    *                  *
>>
>> ****************************************************************************************/
>> -
>> +.file "make_x86_64_sysv_elf_gas.S"
>>   .text
>>   .globl make_fcontext
>>   .type make_fcontext,@function
>>
>>
>>> Alex
>>
>> --
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>


      reply	other threads:[~2018-06-15  7:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-31  6:20 [PATCH] boost: Improve reproducibility mingli.yu
2018-05-31 13:13 ` Richard Purdie
2018-06-01  1:39   ` Yu, Mingli
2018-06-01  5:08     ` Alexander Kanavin
2018-06-01  5:38       ` Yu, Mingli
2018-06-01  8:36         ` Alexander Kanavin
2018-06-05  2:44           ` Yu, Mingli
2018-06-01 17:07         ` Khem Raj
2018-06-01 17:56           ` Alexander Kanavin
2018-06-01 18:33             ` Khem Raj
2018-06-01 19:34               ` Alexander Kanavin
2018-06-15  6:44                 ` Khem Raj
2018-06-15  6:54                   ` Alexander Kanavin
2018-06-15  7:31                     ` Yu, Mingli [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5B236B5C.7060603@windriver.com \
    --to=mingli.yu@windriver.com \
    --cc=alex.kanavin@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.