Hi,
H8SX target supports generation of bit instructions in memory addressing
mode. However, these instructions are not getting generated and the bits
in
memory are operated using other instructions which consume more memory.
The
attached patch "h8sx.patch" generates these bit instructions and h
Hello!
We, the GNU Hurd people, would like to get GCC in a compilable/usable
shape for us again, without needing to do the patching that was needed
since the 4.2 release. I have already some weeks ago sent the needed
patches to the gcc-patches mailing list, where they have been acked by
Paolo and
Thomas Schwinge wrote:
> Hello!
>
> We, the GNU Hurd people, would like to get GCC in a compilable/usable
> shape for us again, without needing to do the patching that was needed
> since the 4.2 release. I have already some weeks ago sent the needed
> patches to the gcc-patches mailing list, wher
On Thu, Nov 6, 2008 at 8:57 AM, Thomas Schwinge <[EMAIL PROTECTED]> wrote:
> Being one of GNU Hurd upstream, I'd offer to fill that position.
I have forwarded this nomination to the GCC Steering Committee.
David
Vladimir Makarov wrote:
Hi, Richard. Returning to accurate cost accumulation issue you found
recently. Here is the patch fixing it. You could try, if you want,
how MIPS will behave with it. The patch also more accurately
calculates ALLOCNO_CALL_FREQ which affects decision to spill allocno
This new failure seems to have been caused by r141613:
+2008-11-05 Martin Jambor <[EMAIL PROTECTED]>
+
+ PR middle-end/37861
+ * tree-ssa-forwprop.c (forward_propagate_addr_expr_1): Don't turn
+ pointer arithmetics into array_ref if the array is accessed
+ through an ind
Naveen H.S. wrote:
Hi,
H8SX target supports generation of bit instructions in memory addressing
mode. However, these instructions are not getting generated and the bits
in
memory are operated using other instructions which consume more memory.
The
attached patch "h8sx.patch" generates these b
Snapshot gcc-4.3-20081106 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/4.3-20081106/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 4.3 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches
You are expecting that the CSS large/small/x-small/etc match those of
TeX.
No, that is not the expectation. (It would be impossible, anyway. All
these things are dynamically changeable in TeX.)
The expectation is that firefox not reduce the size used when
font-size:smaller is specified
