On 09/22/2014 09:06 PM, Andrew Dixie wrote:
- || ((fde_encoding & 0x70) != DW_EH_PE_absptr
- && (fde_encoding & 0x70) != DW_EH_PE_aligned
- && (per_encoding & 0x70) != DW_EH_PE_absptr
- && (per_encoding & 0x70) !=
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,
On Tue, Sep 23, 2014 at 2:47 AM, Joseph S. Myers
wrote:
> If you rename a target macro, the old target macro name needs to be
> poisoned in system.h.
Fixed in patch below.
> This ChangeLog entry seems very incomplete. It doesn't mention the
> changes for other architectures, or to defaults.
On Mon, 22 Sep 2014, Andrew Dixie wrote:
> I altered the dwarf2 frame and exception table generation so the
> decision on whether to use a read-only or read-write section is an
> independent decision from how the frame tables are registered.
> I renamed EH_FRAME_IN_DATA_SECTION to EH_FRAME_THROUGH
Hi,
The following patch moves dwarf2 exception frame tables to read-only
memory so they can be properly shared by multiple processes on AIX.
There are two main mechanisms to register frame tables:
- EH_FRAME_SECTION_NAME puts the frames in a specially named section,
which are then registered by c
