Ilya Enkovich writes:
> - When we pass (return) pointer on register, we use the next
> available bound register to pass (return) bounds
>From the wording, it seems function pointers get bounds too.
If so, it might be good to state that explicitly.
I suppose they would be all-of-memory bounds th
peliculas
series de tv
recitales
discografias completas
juegos para todas las consolas
aplicaciones para todos los operativos
buscanos con el nombre xtop
On 08/26/13 01:40, Senthil Kumar Selvaraj wrote:
It isn't any kind of workaround the above. Apple tools are simply so buggy
that they can't grok DWARF later than 2, crash in lots of ways on it.
Why do you want DWARF2 rather than DWARF3 or 4?
Same reason, some tools (proprietary debugger etc..
Hi,
Here is a patch to extend x86-64 psABI to support MPX [1].
A short description of changes:
- There are 4 bound registers (bnd0-bnd3) added; all of them are caller-save
- When we pass (return) pointer on register, we use the next
available bound register to pass (return) bounds
- If there i
On Mon, Aug 26, 2013 at 05:29:36PM +0400, Michael V. Zolotukhin wrote:
> > Nope, there is only one target data pragma, so you would use here just:
> >
> > struct data_descriptor data_desc2[2] = { ... };
> > GOMP_target (-1, bar.omp_fn.1, "bar.omp_fn.1", data_desc2, 2);
> This 'pragma target' i
> Actually, not two versions of those during the compilation, you have
> just one v and one tgt, both have __attribute__(("omp declare target"))
> on them (note, you can't specify that attribute manually).
> And just when streaming into .gnu.target_lto_* sections you only stream
> everything that h
On Mon, Aug 26, 2013 at 03:59:11PM +0400, Michael V. Zolotukhin wrote:
> As I currently see it, the given code would be expanded to something like
> this:
>
> // Create two versions of V: for host and for target
> int v;
> int v_target __attribute(target);
>
> // The same for TGT function
> No need for the device and handler IMHO, each vector would correspond to
> one function call (GOMP_target, GOMP_target_data or GOMP_target_update)
> and all those calls would be called with device id.
Probably yes.
> Let's talk about some concrete example (though, I see the gimplifier
> doesn't
Hi!
On Tue, 2013-08-20 11:24:31 +0400, Alexander Ivchenko
wrote:
> Hi, thanks for cathing this.
>
> I certainly missed that OPTION_BIONIC is not defined for linux targets
> that do not include config/linux.h in their tm.h.
>
> This patch fixed build for powerpc64le-linux and mn10300-linux.
> l
On Mon, Aug 26, 2013 at 10:23:24AM +0200, Jakub Jelinek wrote:
> On Mon, Aug 26, 2013 at 01:42:18PM +0530, Senthil Kumar Selvaraj wrote:
> > The help text for the --with-dwarf2 configure option says it forces
> > the default debug format to be DWARF 2. However, the built compiler
> > still pr
On Mon, Aug 26, 2013 at 01:42:18PM +0530, Senthil Kumar Selvaraj wrote:
> The help text for the --with-dwarf2 configure option says it forces
> the default debug format to be DWARF 2. However, the built compiler
> still produces DWARF 4, unless -gdwarf-2 is explicitly specified when
> compi
Hi,
The help text for the --with-dwarf2 configure option says it forces
the default debug format to be DWARF 2. However, the built compiler
still produces DWARF 4, unless -gdwarf-2 is explicitly specified when
compiling.
I see that the darwin target gets around this by using the
SUBSU
For the RTEMS wiki, we require a 50 word bio and manually approve accounts. It
is effort to approve accounts but less than the spam clean up was.
It is sad either way.
--joel
Dodji Seketeli wrote:
Jonathan Wakely a écrit:
> I've reverted or deleted all the spam I could find (and that you
>
Jonathan Wakely a écrit:
> I've reverted or deleted all the spam I could find (and that you
> hadn't already done) and have added lots of people to the EditorGroup
> who had made good changes in the past.
Thank you for doing this. It's appreciated.
--
Dodji
14 matches
Mail list logo
