Hi,
The following patch substantially reduces the memory requirements of
GCC compiled C++ programs on AIX.
Currently there are two different pieces of code to decide if a
read-only or a read-write section is required for exception
information:
- If the target supports named sections, there is goo
Hi David,
As discussed, I have updated the to use SYMBOL-$ syntax for
PC-relative addressing and to use a new symbol, __gcc_unwind_dbase,
rather than overloading __dso_handle.
Regards,
Andrew
2014-09-09 Andrew Dixie
Move exception tables to read-only memory on AIX.
* collect2
Hi David,
On AIX, mixing objects from different GCC versions should work as long
as the newest GCC is used for linking. I tested a library with some
objects compiled by GCC-4.4 and some objects compiled by a patched
GCC-5.0. Exceptions passed through the mixed objects without issue.
Did you have
_ONLY 0 should make it see no semantic
changes.
I believe I have an OK for the AIX changes:
https://gcc.gnu.org/ml/gcc-patches/2014-09/msg01305.html.
Can I please have a review for the dwarf2 changes?
Thanks,
Andrew
2014-09-22 Andrew Dixie
Move exception tables to read-only memory o
hitectures, or to defaults.h, or to the
> documentation, for example.
I believe the changelog below covers everything now.
Regards,
Andrew
2014-09-23 Andrew Dixie
Move exception tables to read-only memory on AIX.
* defaults.h (EH_FRAME_SECTION_NAME): Make dependent on
EH_FR
the data segment, so this patch uses
the symbol __dso_handle as an arbitrary base for the data relative
offsets.
I'm considering changing the base to be the TOC.
I'm Interested in thoughts or ideas on a better base for the data
relative offsets?
Thanks,
Andrew
2014-07-25 Andrew Dixie
Hi David,
On Thu, Jul 31, 2014 at 2:22 PM, David Edelsohn wrote:
> As the comment in the code states DWARF2 unwind info was placed in the
> data section to prevent the AIX linker from garbage collecting it.
> How are you avoiding that problem?
That comment is very old. I'm not sure what the ori
