Hi:
My wind river kernel version is 4.1 and the gcc version is
5.2.0 in it.how can I update the gcc tool to 6.0 or upper version?
> Is this something the back end is responsible for getting right, for example
> via the machine description file? If so, any hints where to start?
The SUBREG of MEM is invalid at this stage.
--
Eric Botcazou
I'm doing cleanup on the pdp11 back end to get rid of a
number of ICE in the test suite. One is in
gcc.c-torture/compile/20001221.c -- it works in GCC 4 but
fails in GCC 5 and later.
In the dumps, I see in the output from the expand phase a
large number of memory reference via the "virtual-st
Snapshot gcc-7-20180524 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/7-20180524/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 7 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-7
aldrich [4
A fix for 84851 - missing -Wclass-memaccess for a memcpy in a copy
ctor with a non-trivial member was implemented but disabled for GCC
8 but because it was late, with the expectation we would enable it
for GCC 9. The attached removes the code that guards the full fix
to enable it.
Martin
PR c++/
> See stor-layout.c (compute_record_mode), particularly this section:
>
>/* If we only have one real field; use its mode if that mode's size
> matches the type's size. This only applies to RECORD_TYPE. This
> does not apply to unions. */
>if (TREE_CODE (type) == RECORD_TYPE
On Wed, May 23, 2018 at 08:33:13PM -0400, Paul Koning wrote:
> > On May 23, 2018, at 5:46 AM, Richard Biener
> > wrote:
> >> 2. The reported costs for the various insns are
> >> r22:HI=['x']6
> >> cmp(r22:HI,r23:HI) 4
> >> cmp(['x'],['y'])16
> >>
I've written a patch to fix the transparent_union attribute when the first
field in a union is MODE_PARTIAL_INT, but I noticed that the current code
only allows the TYPE_MODE of a UNION_TYPE to be of MODE_INT class.
See stor-layout.c (compute_record_mode), particularly this section:
/* If we o
On Wed, 2018-05-16 at 22:11 +0100, Richard Sandiford wrote:
>
> TARGET_HARD_REGNO_CALL_PART_CLOBBERED is the only current way
> of saying that an rtl instruction preserves the low part of a
> register but clobbers the high part. We would need something like
> Alan H's CLOBBER_HIGH patches to do i
公 司 可 对 外 开 发 票 ，正 规 可 查 验 。 点 水 优 惠 。
Q Q ：160一852一5627
-
灿烂的群星在整个宇宙中静静地看着他们
在院子里血流了一圈……
On 05/23/2018 02:55 PM, Michael Matz wrote:
On Fri, 18 May 2018, Richard Biener wrote:
Interesting. Do they allow merging across such sections? Consider a 8
byte entity 0x12345678 and 4 byte entities 0x1234 0x5678, will the 4
byte entities share the rodata with the 8 byte one?
There's no l
12 matches
Mail list logo
