Discussion:
opcode headers
Alexander Fedotov
2018-03-20 10:39:23 UTC
Permalink
Can anyone explain for what purpose opcode headers from binutils are
living in "/include/opcode" folder?

Best regards,
Alex
Jon Beniston
2018-03-20 10:44:07 UTC
Permalink
Hi Alex,

They're used by binutils and gdb. Probably not needed for newlib.

Cheers,
Jon

-----Original Message-----
From: newlib-***@sourceware.org [mailto:newlib-***@sourceware.org] On Behalf Of Alexander Fedotov
Sent: 20 March 2018 10:39
To: ***@sourceware.org
Subject: opcode headers

Can anyone explain for what purpose opcode headers from binutils are living in "/include/opcode" folder?

Best regards,
Alex
Alexander Fedotov
2018-03-20 10:46:59 UTC
Permalink
Hi Jon

Yes I know about binutils :)
Question is regarding to newlib. Maybe some history here. Should we
remove them ?
Post by Jon Beniston
Hi Alex,
They're used by binutils and gdb. Probably not needed for newlib.
Cheers,
Jon
-----Original Message-----
Sent: 20 March 2018 10:39
Subject: opcode headers
Can anyone explain for what purpose opcode headers from binutils are living in "/include/opcode" folder?
Best regards,
Alex
--
Best regards,
AF
Jeff Johnston
2018-03-20 16:54:21 UTC
Permalink
Newlib has shared folders with other sourceware projects such as gcc, gdb,
and binutils. They are maintained in their
respective projects and copied. If you take a look at the top-level
MAINTAINERS file you can see where you must send changes
to such shared files. Just because they are shared doesn't mean they are
used by every component. However, if you wanted to
merge to create a unified source directory that could build multiple
components (e.g. gcc, newlib, binutils), you only need to link in the
non-shared
folders into one. See https://sourceware.org/newlib/faq.html#q3

-- Jeff J.
Post by Alexander Fedotov
Can anyone explain for what purpose opcode headers from binutils are
living in "/include/opcode" folder?
Best regards,
Alex
Loading...