The problem was not in the patch, which I've applied. Patch is good. The
problem was in t-mips config file.
Now I have a gcc 3.3.6 compiler working with multilib correctly.
Thanks
Hello,
Could anyone explain to me what is difference between vec_shl_ and
ashl3 patterns? It seems to me that both shift a vector operand 1
with scalar operand 2. I tried to understand some targets' implemenation,
e.g., ia64 as follows, and cannot grasp their difference. Does the "whole
vector
"Bingfeng Mei" writes:
> Could anyone explain to me what is difference between
> vec_shl_ and ashl3 patterns? It seems to me
> that both shift a vector operand 1 with scalar operand 2.
The difference is that with a vector mode gcc will look for the standard
name vec_shl_MODE, and with a non-vect
Ian,
Thanks for prompt reply. Just out of curiosity. Isn't this naming convention
for shift instructions inconsistent with other patterns? For example, we can
define add3 and GCC will automatically use it by vectorization or
in plus expression of two vector types. Why does shift need special na
On Mon, Feb 9, 2009 at 1:57 PM, Joseph S. Myers wrote:
> Status
> ==
>
> Trunk remains in Stage 4 (regression and documentation fixes mode).
>
> GCC 4.4 will be branched when there are no open P1 regressions for 4.4
> and the runtime library sources have been converted to GPLv3 with the
> new
"Bingfeng Mei" writes:
> Thanks for prompt reply. Just out of curiosity. Isn't this naming
> convention for shift instructions inconsistent with other patterns?
> For example, we can define add3 and GCC will
> automatically use it by vectorization or in plus expression of two
> vector types. Why
Bingfeng Mei wrote:
> Hello,
> Could anyone explain to me what is difference between
> vec_shl_ and ashl3 patterns? It seems to me
> that both shift a vector operand 1 with scalar operand 2. I tried to
> understand some targets' implemenation, e.g., ia64 as follows, and
> cannot grasp their diffe
hello!
as this is my first time adding some noise to this list, let me briefly
introduce myself: Jaka; member of a team porting gcc to the NEC SX
architecture ( http://code.google.com/p/sx-gcc/ ).
really close now to a working C compiler, only a few testcases still
failing.
however, I have a pro
I am looking at a related problem in GCSE, GCC 4.3 whereby constants
are propagated to their use irrespective of the final instruction cost
of generating them (machine cycles or instruction count).
Global constant propagation effectively voids common expressions that
form large constants, identifi
In a recent upgrade, we noticed that -I- functionality is being
replaced with -iquote. This -iquote does not have the same
functionality as -I- and is removing a strong function that is needed.
-I- provides the ability to have include files (.h) reference files in
the same directory and yet use t
>In a recent upgrade, we noticed that -I- functionality is being
>replaced with -iquote. This -iquote does not have the same
>functionality as -I- and is removing a strong function that is needed.
I wasn't around for the decision to remove the "don't search the
directory containing the current fi
Jaka Močnik writes:
> in emit_library_call_value_1(), local var stack_usage_map_buf is
> allocated with
>
> stack_usage_map_buf = XNEWVEC (char, highest_outgoing_arg_in_use);
> stack_usage_map = stack_usage_map_buf;
>
> allocating a buffer with 1 char for each byte of stack required for
> out
12 matches
Mail list logo
