Richard Sandiford writes:
> Matthew Fortune writes:
> >> > With these defaults, the closest supported ABI is used for each
> >> > architecture based on the --with-o32-fp build option. The only one
> >> > I really care about is the middle one as it makes full use of the
> >> > O32 FPXX ABI without
Matthew Fortune writes:
>> > With these defaults, the closest supported ABI is used for each
>> > architecture based on the --with-o32-fp build option. The only one I
>> > really care about is the middle one as it makes full use of the O32
>> > FPXX ABI without a user needing to account for arch r
Am Mon, 17 Mar 2014 09:44:53 +0100
schrieb Richard Biener :
> On Sun, Mar 16, 2014 at 3:58 AM, Martin Uecker
> wrote:
> >
> > Hi list,
> >
> > the strings in the ".debug_str" section are output
> > in an arbitrary order. Could this be changed?
> >
> > The function 'output_indirect_strings' in 'g
Hi Mircea,
thank you for your comment! I wanted to say, that this AST-like
representation is an ISL AST containing only loops, conditions, and
statements (basic blocks). It will be differ from a CLooG AST in
representation of AST and, possibly, additional options of ISL AST
generation.
I'll try t
At the company where I work, we have a large program using Boost
Python (1.54). We do our product builds for RHEL 5 and recently
started building using gcc 4.8 from RedHat devtoolset 2 for
performance. This works well, except for one system where it would
deterministically crash. I traced it to an
Hi,
First, I fully agree that integration of the ISL code generator into Graphite
will be an
important step forward for Graphite development.
Regarding the implementation I have a question - why a new AST-like
representation is needed ?
It is not possible to generate the code directly from the
Why is jump_table_data an active_insn?
int
active_insn_p (const_rtx insn)
{
return (CALL_P (insn) || JUMP_P (insn)
|| JUMP_TABLE_DATA_P (insn) /* FIXME */
|| (NONJUMP_INSN_P (insn)
&& (! reload_completed
|| (GET_CODE (PATTERN (insn)) != USE
In our case, we make MAC register explicit by defining a new
type of register (data type). To use your mac instruction, you must have
a first instruction to only write to the mac register. In the
following mac builtins, the mac register can be both input/output
and therefore dependency is respected
On Mon, Mar 17, 2014 at 1:59 AM, Hariharan Sandanagobalane
wrote:
> Hello,
> This question is similar to one raised by bingfeng here
>
> http://gcc.gnu.org/ml/gcc/2010-04/msg00241.html
>
> In our private port based on GCC 4.8.1, i want to define a builtin function
> for multiply and accumulate. Th
On Sun, Mar 16, 2014 at 1:21 PM, Prathamesh Kulkarni
wrote:
> In c_expr::c_expr, shouldn't OP_C_EXPR be passed to operand
> constructor instead of OP_EXPR ?
Indeed - I have committed the fix.
Thanks,
Richard.
> This caused segfault for patterns when "simplification" operand was
> only c_expr (p
On Sun, Mar 16, 2014 at 3:58 AM, Martin Uecker wrote:
>
> Hi list,
>
> the strings in the ".debug_str" section are output
> in an arbitrary order. Could this be changed?
>
> The function 'output_indirect_strings' in 'gcc/dwarf2out.c'
> uses htab_traverse which then outputs the string in the
> orde
11 matches
Mail list logo