Maxim Kuvyrkov writes:
> Updated patch attached. Any further comments?
It's due to my bad explanation, sorry, but this isn't what I meant.
The two main changes I was looking for were:
1) Your pattern uses:
[(mem:GPR (match_operand:P 1 "register_operand" "d"))]
Instead, we should d
Hi,
If ENABLE_BUILD_WITH_CXX is defined, then GCC itself is built with C++,
and we want a C++ signature for functions. If it is not defined, then
GCC itself is not built with C++, and we want (and must have) a C
signature.
I suppose we would decide that fancy_abort always uses a C signature,
b
Om 13.06.2012 10:00, Tobias Burnus wrote:
This patch fixes issues with deferred length strings, where the new
string length (= RHS len) is evaluated too late. That's fixed by
calling gfc_add_block_to_block. I have no idea whether the condition
makes sense or whether that function could always b
http://gcc.gnu.org/ml/fortran/2012-05/msg00171.html
On 30.05.2012 13:56, Tobias Burnus wrote:
On 05/30/2012 11:09 AM, Tobias Burnus wrote:
This patch rejects actual arguments to MOVE_ALLOC which are coindexed
or have a corank.
Updated version (cf. below). Build and regtested on x86-64-linux.
http://gcc.gnu.org/ml/fortran/2012-05/msg00173.html
On 30.05.2012 18:35, Tobias Burnus wrote:
This patch is related to today's check.c patch, but independent (also
order wise).
The patch ensures that for scalar coarrays, the array path is taken in
trans-intrinsic. Thus, "to->data = from->data
For details, see PR.
Build and regtested on x86-64-gnu-linux.
OK for the trunk?
Tobias
2012-06-16 Tobias Burnus
PR fortran/53692
* trans-array.c (set_loop_bounds): Don't scalarize via absent
optional arrays.
* resolve.c (resolve_elemental_actual): Don't stop resolving after printing
a w
This patch adds run-time support for the RANK intrinsic. That's
currently a bit pointless as the rank is known at compile time and,
thus, the new code is unreachable as simplify.c handles it.
However, it becomes useful for assumed-rank arrays ("dimension(..)") of
TS 29113. I tested it by disab
> @@ -179,7 +179,11 @@ extern const unsigned char
> mode_class[NUM_MACHINE_MODES];
>
> extern CONST_MODE_SIZE unsigned char mode_size[NUM_MACHINE_MODES];
> #define GET_MODE_SIZE(MODE)((unsigned short) mode_size[MODE])
> -#define GET_MODE_BITSIZE(MODE) ((unsigned short) (GET_MODE_SIZE (MODE) *
Two rather simple patches.
Build and regtested on x86-64-linux.
As one of the issues is a 4.7/4.8 regression:
OK for the trunk and 4.7?
Tobias
2012-06-16 Tobias Burnus
PR fortran/53691
PR fortran/53685
* check.c (gfc_calculate_transfer_sizes): Return if
SIZE= is not constant or source-si
To cleanup my local trees; I had the patch lingering there for a many weeks.
User visible, it only adds parsing support for "dimension(..)" and a
sorry message.
Internally, it implements a basic support for assumed-shape arrays.
There are still many constraint checks missing, scalar actual ar
Roland McGrath writes:
> On Thu, Jun 14, 2012 at 1:13 PM, Mike Stump wrote:
>> On Jun 14, 2012, at 10:16 AM, Roland McGrath wrote:
>>> But if e.g. I use -ffixed-r9 then I think it's a reasonable expectation
>>> that no code is generated that touches r9 in any way, shape, or form.
>>
>> Also, I ca
On Sat, May 5, 2012 at 3:23 PM, H.J. Lu wrote:
> On Thu, May 3, 2012 at 11:15 AM, Richard Sandiford
> wrote:
>> Ping for this patch to always supply a mode to plus_constant:
>>
>> http://gcc.gnu.org/ml/gcc-patches/2012-04/msg00892.html
>>
>> I've done a diff of the changes since the original t
Hi!
Intel folks, the bid_functions.h change is for you, that one plus the
other changes are for GCC.
libgcc/config/libbid/
* bid_functions.h: Check for __GLIBC__ additionally to LINUX when
defining format specifiers.
config/
* dfp.m4 (enable_decimal_float): Enable for i?8
On Sat, Jun 16, 2012 at 7:32 AM, Thomas Schwinge
wrote:
> Hi!
>
> Intel folks, the bid_functions.h change is for you, that one plus the
> other changes are for GCC.
>
> libgcc/config/libbid/
> * bid_functions.h: Check for __GLIBC__ additionally to LINUX when
> defining format specifi
Hello!
This is a backport of upstream boehm-gc configuration support for
GNU/Hurd. The equivalent thing has been used in Debian's GCC packages
since GCC 4.2 already, and I decided that *NOW* ought to be the time to
put it into the GCC tree.
That patch has mostly be done by Samuel Thibault .
boe
On Thu, Aug 4, 2011 at 9:47 AM, Ira Rosen wrote:
> On 19 July 2011 09:44, Ira Rosen wrote:
>> Hi,
>>
>> This patch tries to reduce over-promotion of vector operations that
>> could be done with narrower elements, e.g., for
>>
>> char a;
>> int b, c;
>> short d;
>>
>> b = (int) a;
>> c = b << 2;
>
On Sun, Apr 1, 2012 at 11:51 PM, Ramana Radhakrishnan
wrote:
> On 1 April 2012 23:55, David Edelsohn wrote:
>>> If there are no further comments I am inclined to commit this
>>> patch early next week (possibly causing quite some fallout ...).
>>
>> I am glad there was not more fallout. Unfortuna
Hi Tobias,
Build and regtested on x86-64-linux.
OK for the trunk?
Tobias
OK.
Thanks a lot for the patch!
Thomas
2012-06-16 Ville Voutilainen
Parse virt-specifiers after late-specified return types.
* parser.c (cp_parser_direct_declarator): Move virt-specifier parsing
after late-specified return type parsing
* override4.C: new
Git is doing weird things with my test, its diff
On Sat, Jun 16, 2012 at 3:54 AM, Duncan Sands wrote:
> Hi,
>
>
>>> If ENABLE_BUILD_WITH_CXX is defined, then GCC itself is built with C++,
>>> and we want a C++ signature for functions. If it is not defined, then
>>> GCC itself is not built with C++, and we want (and must have) a C
>>> signature.
On Fri, Jun 15, 2012 at 3:21 PM, Alexandre Oliva wrote:
> On Jun 14, 2012, "H.J. Lu" wrote:
>
>> On Tue, Jun 12, 2012 at 1:42 PM, Richard Henderson wrote:
>>> On 2012-06-05 12:33, Alexandre Oliva wrote:
for gcc/ChangeLog
from Alexandre Oliva
PR debug/49888
21 matches
Mail list logo
