Re: [patch 0/2] PR49847: Add hook to place read-only lookup-tables in named address-space

2017-08-18 Thread Georg-Johann Lay
On 18.08.2017 12:01, Richard Biener wrote: On Wed, Aug 16, 2017 at 3:32 PM, Georg-Johann Lay wrote: On 28.07.2017 09:34, Richard Biener wrote: On Thu, Jul 27, 2017 at 3:32 PM, Georg-Johann Lay wrote: On 27.07.2017 14:34, Richard Biener wrote: On Thu, Jul 27,

Re: [patch 0/2] PR49847: Add hook to place read-only lookup-tables in named address-space

2017-08-18 Thread Richard Biener
On Wed, Aug 16, 2017 at 3:32 PM, Georg-Johann Lay wrote: > On 28.07.2017 09:34, Richard Biener wrote: >> >> On Thu, Jul 27, 2017 at 3:32 PM, Georg-Johann Lay wrote: >>> >>> On 27.07.2017 14:34, Richard Biener wrote: On Thu, Jul 27, 2017 at 2:29 PM,

Re: [patch 0/2] PR49847: Add hook to place read-only lookup-tables in named address-space

2017-08-16 Thread Georg-Johann Lay
On 28.07.2017 09:34, Richard Biener wrote: On Thu, Jul 27, 2017 at 3:32 PM, Georg-Johann Lay wrote: On 27.07.2017 14:34, Richard Biener wrote: On Thu, Jul 27, 2017 at 2:29 PM, Georg-Johann Lay wrote: For some targets, the best place to put read-only lookup

Re: [patch 0/2] PR49847: Add hook to place read-only lookup-tables in named address-space

2017-07-28 Thread Georg-Johann Lay
Richard Biener schrieb: On Fri, Jul 28, 2017 at 12:18 PM, Georg-Johann Lay wrote: Richard Biener schrieb: On Thu, Jul 27, 2017 at 3:32 PM, Georg-Johann Lay wrote: On 27.07.2017 14:34, Richard Biener wrote: On Thu, Jul 27, 2017 at 2:29 PM, Georg-Johann Lay

Re: [patch 0/2] PR49847: Add hook to place read-only lookup-tables in named address-space

2017-07-28 Thread Richard Biener
On Fri, Jul 28, 2017 at 12:18 PM, Georg-Johann Lay wrote: > Richard Biener schrieb: > >> On Thu, Jul 27, 2017 at 3:32 PM, Georg-Johann Lay wrote: >>> >>> On 27.07.2017 14:34, Richard Biener wrote: On Thu, Jul 27, 2017 at 2:29 PM, Georg-Johann Lay

Re: [patch 0/2] PR49847: Add hook to place read-only lookup-tables in named address-space

2017-07-28 Thread Georg-Johann Lay
Richard Biener schrieb: On Thu, Jul 27, 2017 at 3:32 PM, Georg-Johann Lay wrote: On 27.07.2017 14:34, Richard Biener wrote: On Thu, Jul 27, 2017 at 2:29 PM, Georg-Johann Lay wrote: For some targets, the best place to put read-only lookup tables as generated by

Re: [patch 0/2] PR49847: Add hook to place read-only lookup-tables in named address-space

2017-07-28 Thread Richard Biener
On Thu, Jul 27, 2017 at 3:32 PM, Georg-Johann Lay wrote: > On 27.07.2017 14:34, Richard Biener wrote: >> >> On Thu, Jul 27, 2017 at 2:29 PM, Georg-Johann Lay wrote: >>> >>> For some targets, the best place to put read-only lookup tables as >>> generated by

Re: [patch 0/2] PR49847: Add hook to place read-only lookup-tables in named address-space

2017-07-27 Thread Georg-Johann Lay
On 27.07.2017 14:34, Richard Biener wrote: On Thu, Jul 27, 2017 at 2:29 PM, Georg-Johann Lay wrote: For some targets, the best place to put read-only lookup tables as generated by -ftree-switch-conversion is not the generic address space but some target specific address space.

Re: [patch 0/2] PR49847: Add hook to place read-only lookup-tables in named address-space

2017-07-27 Thread Richard Biener
On Thu, Jul 27, 2017 at 2:29 PM, Georg-Johann Lay wrote: > For some targets, the best place to put read-only lookup tables as > generated by -ftree-switch-conversion is not the generic address space > but some target specific address space. > > This is the case for AVR, where for

[patch 0/2] PR49847: Add hook to place read-only lookup-tables in named address-space

2017-07-27 Thread Georg-Johann Lay
For some targets, the best place to put read-only lookup tables as generated by -ftree-switch-conversion is not the generic address space but some target specific address space. This is the case for AVR, where for most devices .rodata must be located in RAM. Part #1 adds a new, optional target