Paulo,
GCC schedule is not particularly designed for VLIW architectures, but it
handles them reasonably well. For the example of your code both schedules take
same time to execute:
38: 0: r1 = e[r0]
40: 4: [r0] = r1
41: 5: r0 = r0+4
43: 5: p0 = r1!=0
44: 6: jump p0
and
38: 0: r1 = e[r0]
41:
2013/7/16 Hendrik Greving :
> Along the same lines, what's the difference of target_flags (I know
> from old compilers) and target_flags_explicit (I do not know)?
>
> Thanks,
> Regards,
> Hendrik Greving
>
> On Mon, Jul 15, 2013 at 10:30 AM, Hendrik Greving
> wrote:
>> Hi,
>>
>> when defining targ
The gcc prereq page says gettext 0.14.5 is the minimum version, but
po/zh_TW.po has lines like this:
#, fuzzy
#~| msgid "Unexpected EOF"
#~ msgid "Unexpected type..."
#~ msgstr "未預期的型態…"
The | syntax appears to have been added in gettext 0.16, and gettext
0.14 can't process it.
Seems to have be
Along the same lines, what's the difference of target_flags (I know
from old compilers) and target_flags_explicit (I do not know)?
Thanks,
Regards,
Hendrik Greving
On Mon, Jul 15, 2013 at 10:30 AM, Hendrik Greving
wrote:
> Hi,
>
> when defining target options with Mask() and "Target" going to
>
Hi,
when defining target options with Mask() and "Target" going to
target_flags. Can I use Init(1) to define the default, or is "Init"
only used to initialize "Var(name)" kind of options? If so, what's the
proper way to define defaults, it wasn't clear to me when checking
mips/i386 definitions for
Ping.
Hi,
I’ve recently started to work on libgomp with the goal of proposing
a new way of handling queues of tasks based on the work done by a
PhD student.
While working on libgomp’s code I noticed two things that puzzled me:
- The code uses gcc’s atomic builtins but doesn’t use the
__
