Hi,
I have done porting of GNU binutils for a new architecture.
Can you tell me if I have to do any changes for dwarf, while porting.
Thanks,
Parul
___
bug-binutils mailing list
bug-binutils@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-binutils
Thanks, I'll check it out.
On 11-Oct-2017 5:43 PM, "Nick Clifton" wrote:
> Hi Parul,
>
> > Can someone help me, how can I check what all changes are done from 2.26
> to 2.27.
> > I do not know how to use git.
> > I want to know what all changes are done for x86-64.
>
> I am not a git expert eith
Hi,
I had done porting using binutils 2.26.
Now I want to move to binutils 2.27.
Can someone help me, how can I check what all changes are done from 2.26 to
2.27.
I do not know how to use git.
I want to know what all changes are done for x86-64.
Thanks,
Parul
__
Hi,
I found that a new option "-mfence-as-lock-add" is added in binutils 2.27.
It generate lock instruction when "-mfence-as-lock-add=yes". Otherwise,
mfence, lfence, sfence is generated.
Please let me know why this option is required. Why lock instruction is
needed.
Thanks,
Parul
___
Hi,
I am porting binutils to my new architecture. I have made changes similar
to one of the architecture which GNU binutils already supports.
I am also able to do testing of binutils using dejaGNU. But, there are few
options for which I am stuck up and not able to test these options. These
are as