GCC internals conditional execution macro?

2013-09-16 Thread Nicklas Bo Jensen
Hi, In GCC internals for GCC 4.8.1 and trunk the section "Macros to control conditional execution" mentions that there exists a macro, but does not name the macro? Which macro is thought of here? The section can be seen here: http://gcc.gnu.org/onlinedocs/gccint/Cond-Exec-Macros.html Thanks, Nic

Re: GCC internals conditional execution macro?

2013-09-16 Thread Andreas Schwab
Nicklas Bo Jensen writes: > In GCC internals for GCC 4.8.1 and trunk the section "Macros to > control conditional execution" mentions that there exists a macro, but > does not name the macro? Which macro is thought of here? The macro has been removed in r188983 without removing the now empty sec

Re: Questions about LTO infrastructure and pragma omp target

2013-09-16 Thread Ilya Verbin
Hi Richard, On 23 Aug 14:24, Richard Biener wrote: > Ilya Verbin wrote: > >I'm trying to implement the approach with modified lto-wrapper. > >Suppose we have a bytecode of the routine foo, streamed during ompexp > >pass into some section, say .gnu.omptarget_foo. > >In function lto.c:do_whole_prog

Re: MPX ABI extension

2013-09-16 Thread Ilya Enkovich
Ping 2013/8/27 Ilya Enkovich : > 2013/8/27 Kalle Olavi Niemitalo : >> 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 mig

Re: [RFC] Offloading Support in libgomp

2013-09-16 Thread Jakub Jelinek
On Fri, Sep 13, 2013 at 01:34:43PM +0400, Michael Zolotukhin wrote: > 1.2. Linking > > When all source files are compiled, a linker is invoked. The linker is passed > a special option to invoke openmp-plugin. The plugin is responsible for > producing target-side executables - for each target it

memory allocation

2013-09-16 Thread zhaobin xv
Hi As I know in C : a. Global and static variables locate at data segment b. When a function is called, memory is allocated on the stack to hold parameter values, local variables, and the address of the calling function c. the struct is aligned based on the greatest alignment requirement of it's me