rite access to the GCC SVN repository, so if this patch
is satisfactory, I would appreciate if someone could commit it for me.
Thanks.
---
2017-02-XX Jozef Lawrynowicz <joze...@somniumtech.com>
gcc/
PR target/78838
* config/msp430/msp430.c (gen_prefix): Return NULL when section name is .lowtext
r244727 and r243310 from the gcc trunk are needed in the gcc-6-branch
to build gcc for the msp430 target with C and C++ support.
Would it be possible for these patches to be backported to the
gcc-6-branch? The gcc-5-branch builds for msp430 with C and C++
support, so isn't this technically a
ied.
From b5aacd74cdd4209f28309d38d85cb0004cc93410 Mon Sep 17 00:00:00 2001
From: Jozef Lawrynowicz <joze...@somniumtech.com>
Date: Thu, 30 Mar 2017 15:46:26 +
Subject: [PATCH 1/2] Backport r244727
2017-01-20 Joe Seymour <jo...@somniumtech.com>
* acinclude.m4 (GLIBCXX_CHECK_SIZE_T_MANGLING): Support
rite access to the GCC SVN repository, so if this patch
is satisfactory, I would appreciate if someone could commit it for me.
Thanks.
---
2017-02-XX Jozef Lawrynowicz <joze...@somniumtech.com>
gcc/
PR target/78838
* config/msp430/msp430.c (gen_prefix): Return NULL when section name
The attached patch modifies the setting of TYPE_SIZE for __intN types
to use GET_MODE_BITSIZE rather than the bitsize extracted from the N
value. TYPE_SIZE for sizetype and bitsizetype are also modified to use
GET_MODE_BITSIZE rather than the precision of the type.
This fixes an issue for the
On 24 April 2017 at 12:02, Jozef Lawrynowicz <joze...@somniumtech.com> wrote:
> The patch passed bootstrap and regression testing with no regressions
> on recent trunk (r247020) for x86_64-pc-linux-gnu.
> The patch passed regression testing with "-mcpu=msp430x/-mlar
On 01/08/2017 00:08, Joseph Myers wrote:
On Wed, 26 Jul 2017, Jeff Law wrote:
TYPE_SIZE, according to my understanding, should be a tree for the size
of the expression in bits.
The problem is for msp430 that size varies depending on where it's used.
ie, in a register an object might have a
The MSP430 target supports an attribute "persistent" that can be set
on variables to indicate that they should be placed in a special
section ".persistent", which will not be re-initialized on reset.
As reported in PR78818
(https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78818), GCC does not
place
, I would appreciate if someone could commit
it for me as I do not have write access.
2017-05-XX Jozef Lawrynowicz <joze...@somniumtech.com>
gcc/
PR target/78818
* config/msp430/msp430.c (msp430_unique_section): Set section to
.persistent if persistent attribute is set.
gcc
Add warning to back end and add test.
Patch is attached.
If the patch is acceptable, I would appreciate if someone could commit
it for me as I do not have write access.
2017-05-XX Jozef Lawrynowicz <joze...@somniumtech.com>
gcc/
PR target/78818
* config/msp430/ms
On 18 May 2017 at 16:46, Martin Sebor wrote:
> + if (!message && TREE_NAME_EQ (name, ATTR_PERSIST) && !TREE_STATIC (*
> node)
> + && !TREE_PUBLIC (* node) && !DECL_EXTERNAL (* node))
> +message = "%qE attribute has no effect on automatic variables";
>
> In code like
A patch for this bug was originally posted here:
https://gcc.gnu.org/ml/gcc-patches/2017-02/msg01054.html
There were some issues with that patch which I've now fixed.
The MSP430 target supports the automatic placement of functions and
data in different memory regions when passing the
On 26/05/2017 13:01, Jonathan Wakely wrote:
On 22/05/17 17:16 +0100, Jozef Lawrynowicz wrote:
Ping, original post:
https://gcc.gnu.org/ml/gcc-patches/2017-03/msg01560.html
These are both libstdc++ patches and originally posted to the
libstdc++ list, so you'll have more luck mailing that list
Original post: https://gcc.gnu.org/ml/gcc-patches/2017-04/msg01030.html
The attached patch fixes an issue for the msp430 target where the TYPE_SIZE of
the __int20 type was set using the precision (20 bits) instead of the in-memory
size (32 bits) of the type. This bug caused an ICE as reported in
On 19/05/2017 04:13, Martin Sebor wrote:
On 05/18/2017 10:14 AM, Jozef Lawrynowicz wrote:
A patch for this bug was originally posted here:
https://gcc.gnu.org/ml/gcc-patches/2017-02/msg01054.html
There were some issues with that patch which I've now fixed.
The MSP430 target supports
Ping, original post:
https://gcc.gnu.org/ml/gcc-patches/2017-03/msg01560.html
---
For the msp430-elf target, the gcc-6-branch fails to build when
configured to enable C++ support.
The gcc-5-branch successfully builds with C++ support.
Backporting r244727 and r243310 to the gcc-6-branch
nks,
Jozef
From 8a41a45f2f771ae540b16ec007ded499a9ed5244 Mon Sep 17 00:00:00 2001
From: Jozef Lawrynowicz <joze...@somniumtech.com>
Date: Mon, 5 Jun 2017 18:07:22 +
Subject: [PATCH 1/3] MSP430: Check if a variable can have a section before
checking for a section name
2017-06-XX J
On 13/06/2017 16:54, Nick Clifton wrote:
Hi Jozef,
Ok for trunk and gcc-7-branch?
Approved - please apply (to both).
Cheers
Nick
Sorry, didn't mention in that last post that I don't have write access,
could someone please apply this for me.
Thanks,
Jozef
ta instead.
If the patch is acceptable, I would appreciate if someone could commit
it for me, as I do not have write access.
Thanks,
Jozef
From 4ea2f4393929b70eb6e56e1d761b584f65d39248 Mon Sep 17 00:00:00 2001
From: Jozef Lawrynowicz <joze...@somniumtech.com>
Date: Thu, 24 Aug 2017 13:44:11 +
where the
subword is a SYMBOL_REF.
If the patch is acceptable, I would appreciate if someone could commit
it for me, as I do not have write access.
Thanks,
Jozef
From 72a419c1f470254f06c59c7824ae27818a18b555 Mon Sep 17 00:00:00 2001
From: Jozef Lawrynowicz <joze...@somniumtech.com>
Date: T
On 22/08/2017 11:57, Jozef Lawrynowicz wrote:
On 02/08/2017 17:45, Joseph Myers wrote:
On Wed, 2 Aug 2017, Jeff Law wrote:
I think Joseph's suggestion for looking at partial float handling may be
useful, though ia64's RFmode may be more interesting as it's not a
multiple of 8 in bitsize
,
Jozef
From 44b14ffae0e8956f40cd5356a9f00f5d055709c7 Mon Sep 17 00:00:00 2001
From: Jozef Lawrynowicz <joze...@somniumtech.com>
Date: Thu, 24 Aug 2017 11:10:24 +
Subject: [PATCH] MSP430: Prevent lto removing interrupt handlers
2017-08-XX Jozef Lawrynowicz <joze...@somniu
commit
it for me, as I do not have write access.
Thanks,
Jozef
From a1313aeefa289cdf8c7c4b28b04648eed4708716 Mon Sep 17 00:00:00 2001
From: Jozef Lawrynowicz <joze...@somniumtech.com>
Date: Thu, 24 Aug 2017 16:39:29 +
Subject: [PATCH] MSP430: Pass -mcode/data-region to the linker and ass
On 02/08/2017 17:45, Joseph Myers wrote:
On Wed, 2 Aug 2017, Jeff Law wrote:
I think Joseph's suggestion for looking at partial float handling may be
useful, though ia64's RFmode may be more interesting as it's not a
multiple of 8 in bitsize. IF/KF modes on the ppc port have similar
uld commit it
for me, as I don't have write access.
>From 6b7a22144d70bcccfeebc9fcefd724e8f05a6e09 Mon Sep 17 00:00:00 2001
From: Jozef Lawrynowicz <joze...@mittosystems.com>
Date: Wed, 23 May 2018 21:33:45 +0100
Subject: [PATCH] MSP430: Dont warn if naked function does not return
2018-05-23
On 04/06/18 18:52, DJ Delorie wrote:
Jozef Lawrynowicz writes:
For the currently released msp430i* devices, only digits follow the i, so no
upper or lower case conversion is needed.
Thinking of the future... do we expect any new devices with letters?
Should we plan for them? Or better
On 29/05/18 23:55, DJ Delorie wrote:
Jozef Lawrynowicz writes:
If an argument is passed to the interrupt attribute, GCC will create a section
for the interrupt vector when outputting the assembly. This, combined with the
code to ensure the interrupt function doesn't get optimized out, ensures
On 31/05/18 00:28, Jeff Law wrote:
It's not clear why having that subreg is causing incorrect code to be
generated, but the subreg is clearly wrong since it's a qisi pattern not
a hisi pattern. Based on that I've approved and installed the change.
There's some further info in PR85941, but I
access.
>From 18d1980bb4061cee9d97f2b7737af2dfd9e52c34 Mon Sep 17 00:00:00 2001
From: Jozef Lawrynowicz <joze...@mittosystems.com>
Date: Sun, 27 May 2018 12:55:41 +0100
Subject: [PATCH] MSP430: Allow interrupt handlers to be static and fix the
__interrupt__ attribute causing an ICE
2018-05-
On 29/05/18 19:45, DJ Delorie wrote:
The reason I required interrupt handlers to be non-static is because the
linker builds the interrupt handler table using weak references. If the
handler is static, it won't be added to the table, and never called.
So you'd need a test to ensure that the
if someone would commit it for
me, as I don't have write access.
>From 4f96a05f4849e28064f5c202a55b753b59a106ef Mon Sep 17 00:00:00 2001
From: Jozef Lawrynowicz <joze...@mittosystems.com>
Date: Sun, 27 May 2018 21:09:49 +0100
Subject: [PATCH] MSP430: Fix PR39240 execution failure for msp430-
On 04/06/18 18:52, DJ Delorie wrote:
Jozef Lawrynowicz writes:
For the currently released msp430i* devices, only digits follow the i, so no
upper or lower case conversion is needed.
Thinking of the future... do we expect any new devices with letters?
Should we plan for them? Or better
Added myself to write after approval list in MAINTAINERS.
Index: ChangeLog
===
--- ChangeLog (revision 261081)
+++ ChangeLog (revision 261082)
@@ -1,3 +1,7 @@
+2018-06-01 Jozef Lawrynowicz
+
+ * MAINTAINERS (write after
On 06/06/18 17:43, DJ Delorie wrote:
Jozef Lawrynowicz writes:
Word from TI is that the lowercase i is an exception, the rule is to have all
uppercase letters. No further msp430i devices are planned so the rules for
generating device names in this patch shouldn't need any future changes.
So
rom d08160770abef420b6699f6bd2c30a055bd10350 Mon Sep 17 00:00:00 2001
From: Jozef Lawrynowicz
Date: Wed, 6 Jun 2018 18:20:56 +0100
Subject: [PATCH] Document usage of line number 0 in
dg-{warning,error,message,bogus} directives
2018-06-06 Jozef Lawrynowicz
* gcc/doc/sourcebuild.texi: Document usage of line number 0 in ver
On 06/06/18 23:38, DJ Delorie wrote:
That's fine too, I was thinking of checking mcu_name[i] against NUL.
Any of those solutions would work :-)
Thanks, installed on trunk.
On 06/06/18 21:38, DJ Delorie wrote:
+ snprintf (mcu_name, sizeof (mcu_name) - 1, "__%s__", target_mcu);
+ start_upper = 0;
Can optimize this to 2 :-)
Otherwise OK.
Ah yes. Could also do:
- for (i = start_upper; i < strlen (mcu_name); i++)
+ for (i = start_upper; i
On 06/06/18 22:02, DJ Delorie wrote:
Jozef Lawrynowicz writes:
- for (i = start_upper; i < strlen (mcu_name); i++)
+ for (i = start_upper; i < strlen (mcu_name) - 2; i++)
Might be faster to test mcu_name[i] instead of calling strlen repeatedly
too, but this only runs on
the patch is acceptable, I would appreciate if someone would commit it for
me, as I don't have write access.
>From 386f8e6aadf5627fcba0955a8dbb6abcec69b1a5 Mon Sep 17 00:00:00 2001
From: Jozef Lawrynowicz <joze...@mittosystems.com>
Date: Mon, 28 May 2018 13:04:12 +0100
Subject: [PATCH] U
commit it for
me, as I don't have write access.
>From 4b9fc3e0bf3e746c6be95c994f5ea4882dcd3e1d Mon Sep 17 00:00:00 2001
From: Jozef Lawrynowicz <joze...@mittosystems.com>
Date: Wed, 23 May 2018 21:52:24 +0100
Subject: [PATCH] MSP430: Fix -fleading-underscore having no effect
2018-05-
rom: Jozef Lawrynowicz
Date: Mon, 4 Jun 2018 12:04:54 +0100
Subject: [PATCH] MSP430: Fix device name symbol defined for msp430i* devices
2018-06-04 Jozef Lawrynowicz
* gcc/config/msp430/msp430.c (msp430_mcu_name): Set the "i" in the
symbol defined for msp430i* devices to be lowe
On 04/06/18 18:26, DJ Delorie wrote:
Jozef Lawrynowicz writes:
+ if (strncmp (target_mcu, "msp430i", 7) == 0)
+ snprintf (mcu_name, sizeof (mcu_name) - 1, "__MSP430i%s__",
+ target_mcu + 7);
+ else
Do you need to TOUPPER the parts of tar
On 27/05/18 14:19, Jozef Lawrynowicz wrote:
If the patch is acceptable, I would appreciate if someone would commit
it for
me, as I don't have write access.
"msp430.md" in the ChangeLog entry should be "msp430.c".
The following series of patches extends MCU device data handling for the msp430
target, allowing an external file to be read which describes the CPU ISA and
hardware multiply supported for different MCUs.
The current hard-coded solution means that new MCUs can only be supported by
updating the
by the
driver which
places the corresponding mcpu value for the MCU on its command line.
Ok for trunk?
>From 751a5b4f32a91d697b56fa94ca8426fa6679c5fa Mon Sep 17 00:00:00 2001
From: Jozef Lawrynowicz
Date: Thu, 7 Jun 2018 14:44:10 +0100
Subject: [PATCH 1/4] MSP430 - Devices 1 - Handle device ta
The second patch updates the hard-coded MCU data to the latest version.
>From 7da6e1edcffc1fa1a93dde5e23c87f9653132768 Mon Sep 17 00:00:00 2001
From: Jozef Lawrynowicz
Date: Mon, 25 Jun 2018 19:56:53 +0100
Subject: [PATCH 2/4] MSP430 - Devices 1.1 Update hard-coded MCU data
2018-06
.
>From 7e24ade1d4d16d71dca3f4d7d3e66a784d2563fd Mon Sep 17 00:00:00 2001
From: Jozef Lawrynowicz
Date: Tue, 26 Jun 2018 12:21:09 +0100
Subject: [PATCH 3/4] MSP430 - Devices 2 - Add functionality to read device
data from CSV file
2018-06-27 Jozef Lawrynowicz
gcc/config/msp430/
* msp
ces.csv is not found on an include path.
If devices.csv is found using one of these methods, the directory
containing
devices.csv is also registered as an include path and linker library
path.
>From 43a9106e71a8b7545f894b4c1c495288b6144876 Mon Sep 17 00:00:00 2001
From: Jozef Lawrynowicz
Date: Tu
. A further bug prevents
trunk from building for msp430-elf.
If the attached patch is acceptable, I would appreciate if someone would commit
it for me, as I do not have write access.
From 31d8554ebb6afeb2d8f235cf3d3c262236aa5e32 Mon Sep 17 00:00:00 2001
From: Jozef Lawrynowicz <jozefl@gmail.
The instructions on https://gcc.gnu.org/contribute.html#testing for
bootstrapping GCC are incorrect.
The instructions say to run 'make bootstrap' from the top level GCC
directory,
but this results in the below error.
$ make bootstrap
make: *** No rule to make target 'bootstrap'. Stop.
The
Lawrynowicz <jozefl@gmail.com>
Date: Fri, 12 Jan 2018 13:23:40 +
Subject: [PATCH] Add support for Complex Partial Integers - CPSImode
2018-01-XX Jozef Lawrynowicz <jozefl@gmail.com>
gcc/
PR target/79242
* machmode.def: Define a complex mode for PARTIAL_INT.
On 14/02/18 07:25, Jeff Law wrote:
On 02/08/2018 09:54 AM, Jozef Lawrynowicz wrote:
ping x1
Complex Partial Integers are unimplemented, resulting in an ICE when
attempting to use them. https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79242
This results in GCC7/8 for msp430-elf failing to build
?
>From e655a518a06a848dc398504f28272750e1a2be9f Mon Sep 17 00:00:00 2001
From: Jozef Lawrynowicz
Date: Tue, 13 Mar 2018 11:25:56 +
Subject: [PATCH] When aligning to POINTER_SIZE, round alignment to largest
power of 2 that is <= POINTER_SIZE
PR middle-end/86705
* gcc/cfgexpand.c (set_pa
:00 2001
From: Jozef Lawrynowicz
Date: Tue, 24 Jul 2018 23:24:41 +0100
Subject: [PATCH][MSP430] Fix PR86662
2018-07-27 Jozef Lawrynowicz
PR target/86662
* gcc/tree.c (build_common_tree_nodes): Initialize integer_types array
with all enabled __intN types.
* gcc/testsuite/gcc.target/msp
On 30/07/18 14:29, Richard Biener wrote:
On Sun, Jul 29, 2018 at 6:27 PM Jozef Lawrynowicz
wrote:
pr45678-2.c ICEs for msp430-elf with -mlarge, because an alignment of
POINTER_SIZE is attempted. POINTER_SIZE with -mlarge is 20-bits, so further
code in the middle-end that expects
ping x1
Trunk doesn't build for msp430 due to an ICE whilst building libstdc++.
The following patch proposed a while ago fixes the issue, but hasn't been
applied: https://gcc.gnu.org/ml/gcc-patches/2017-08/msg01433.html
I don't have write access, so if the patch is acceptable I would
Trunk doesn't build for msp430 due to an ICE whilst building libstdc++.
The following patch proposed a while ago fixes the issue, but hasn't been
applied: https://gcc.gnu.org/ml/gcc-patches/2017-08/msg01433.html
I don't have write access, so if the patch is acceptable I would appreciate
if
for these attributes, and some other MSP430
attributes, which previously did not have tests.
Ok for trunk?
>From 5c56509cfa0f285549eceefb457dc59134d30d0e Mon Sep 17 00:00:00 2001
From: Jozef Lawrynowicz
Date: Thu, 18 Oct 2018 22:16:22 +0100
Subject: [PATCH] Extend MSP430 data attribute handling
2018-1
-linux-gnu, and
msp430-elf with -mlarge. For msp430-elf with -mlarge, the above DejaGNU tests
are also fixed.
Ok for trunk?
>From cc1ccfcc0d8adf7b0e1ca95a47a8a8e7e12fc99c Mon Sep 17 00:00:00 2001
From: Jozef Lawrynowicz
Date: Mon, 22 Oct 2018 21:02:10 +0100
Subject: [PATCH] Allow union TYPE_M
f29 execute_todo
../../gcc/passes.c:1979
There is a missing cast when the integer literal "1" is used, which causes the
above error. Committed the attached patch as "obvious".
2018-11-01 Jozef Lawrynowicz
gcc/testsuite
* gcc.dg/tree-ssa/cunroll-13.c: Add missing cas
which
places the corresponding mcpu value for the MCU on its command line.
>From 58709e127d3bf13da6da58fca416946718c4c17c Mon Sep 17 00:00:00 2001
From: Jozef Lawrynowicz
Date: Mon, 29 Oct 2018 13:48:06 +
Subject: [PATCH 1/3] MSP430 - Devices 1 - Handle device tasks in separate file
2018-10
The same as previous pings except I removed the patch which updates the
hard-coded device data - I'll commit that later as "obvious".
Ok for trunk?
The following series of patches extends MCU device data handling for the msp430
target, allowing an external file to be read which describes the
d on an include path.
If devices.csv is found using one of these methods, the directory containing
devices.csv is also registered as an include path and linker library path.
>From cc4dbcb83be19fd55e6dae28ea37a714109bec26 Mon Sep 17 00:00:00 2001
From: Jozef Lawrynowicz
Date: Mon, 29 Oct 2018 13:52:39 +0
ed.
>From e85964a398a35a69513da07e4fcdaeed215ae79a Mon Sep 17 00:00:00 2001
From: Jozef Lawrynowicz
Date: Mon, 29 Oct 2018 13:51:24 +
Subject: [PATCH 2/3] MSP430 - Devices 2 - Add functionality to read device
data from CSV file
2018-10-29 Jozef Lawrynowicz
gcc/config/msp430/
* msp430-devices.c (msp430_check_path_for_
The test uses "unsigned long" as the "num" argument to memcpy, but it should be
size_t, and these types are not equivalent on all targets.
Committed to trunk.
>From 3ebbb8102bd9b984c6f1a1eaf0bca45fe4fd23e1 Mon Sep 17 00:00:00 2001
From: Jozef Lawrynowicz
Date: Tue, 6
ping
On 29/10/2018 14:22, Jozef Lawrynowicz wrote:
The same as previous pings except I removed the patch which updates the
hard-coded device data - I'll commit that later as "obvious".
Ok for trunk?
The following series of patches extends MCU device data handling for
the msp
On Thu, 15 Nov 2018 09:48:05 -0500
Paul Koning wrote:
> > On Nov 14, 2018, at 5:19 PM, Jozef Lawrynowicz
> > wrote:
> >
> >
> > I'd be curious if the line I added the xfail to in c-c++-common/pr57371-2.c
> > also fails for pdp11.
> >
> > The co
regtested the attached patch on trunk, and committed.
>From 9e26066f2a0f979a6bea538d27524e03b81618f3 Mon Sep 17 00:00:00 2001
From: Jozef Lawrynowicz
Date: Fri, 2 Nov 2018 20:59:10 +
Subject: [PATCH] [MSP430] Fix register classification of PC, CG1 and CG2
2018-11-06 Jozef Lawrynowicz
e for them.
Successfully bootstrapped and regtested current trunk for x86_64-pc-linux-gnu
and regtested msp430-elf with -mlarge.
Ok for trunk?
>From 48890bd01668f68bafbd94556c9754bf2406 Mon Sep 17 00:00:00 2001
From: Jozef Lawrynowicz
Date: Thu, 8 Nov 2018 13:42:27 +
Subject: [PATCH] Implemen
On Wed, 14 Nov 2018 11:30:39 -0500
Paul Koning wrote:
> > On Nov 14, 2018, at 10:44 AM, Jozef Lawrynowicz
> > wrote:
> >
> > Patch 1 tweaks dg directives in tests specifically for msp430. Many of
> > these are extensions to existing target selectors in dg direct
The following series of patches fixes a number of test failures when running
the GCC DejaGNU testsuite for msp430-elf.
The raw output from contrib/compare_tests is a bit misleading for some tests,
as lines have been added to the source code, changing line numbers for
dg-warning/dg-error tests. I
Patch 1 tweaks dg directives in tests specifically for msp430. Many of
these are extensions to existing target selectors in dg directives.
From a730d945647923c5c10e8487ca3c2a24511abf3d Mon Sep 17 00:00:00 2001
From: Jozef Lawrynowicz
Date: Thu, 8 Nov 2018 18:55:57 +
Subject: [PATCH 1/7
rom ed24754b1d97992400bb374916d87cce151f7e89 Mon Sep 17 00:00:00 2001
From: Jozef Lawrynowicz
Date: Sat, 10 Nov 2018 15:47:21 +
Subject: [PATCH 5/7] [TESTSUITE] Prune messages about ISO C not supporting
__int20 from output of tests
2018-11-14 Jozef Lawrynowicz
gcc/testsuite/ChangeLog:
* gcc
Patch 7 fixes tests for msp430-elf in the large memory model.
>From 494465f13df814bf3daad5e330d2c7139f2db625 Mon Sep 17 00:00:00 2001
From: Jozef Lawrynowicz
Date: Sat, 10 Nov 2018 16:08:44 +
Subject: [PATCH 7/7] [TESTSUITE] Fix tests for msp430-elf large memory model
2018-11-14 Jo
rom 23ab77f7e44e104595adb0b5cabd9caf93141ffd Mon Sep 17 00:00:00 2001
From: Jozef Lawrynowicz
Date: Thu, 8 Nov 2018 22:39:12 +
Subject: [PATCH 3/7] [TESTSUITE] Dynamically check if size_t is large enough
for tests containing large structs/arrays
2018-11-14 Jozef Lawrynowicz
gcc/testsuite/ChangeLog:
* gc
Patch 4 fixes tests when int is 16-bits by default.
>From 62b273f73cd7a4db22b1161f450ae7267d185890 Mon Sep 17 00:00:00 2001
From: Jozef Lawrynowicz
Date: Thu, 8 Nov 2018 23:09:38 +
Subject: [PATCH 4/7] [TESTSUITE] Fix tests when int is 16-bit by default
2018-11-14 Jozef Lawrynow
Patch 2 fixes issues finding libssp when linking tests or checking for
fstack_protector support.
>From 6c6f34bae386a5f396e6f9630514fc7080c2f940 Mon Sep 17 00:00:00 2001
From: Jozef Lawrynowicz
Date: Sun, 11 Nov 2018 14:30:32 +
Subject: [PATCH 2/7] [TESTSUITE] Add path to lib
ol.
>From 15a04e0139ec40196ddb79f1125635029dccae68 Mon Sep 17 00:00:00 2001
From: Jozef Lawrynowicz
Date: Sat, 10 Nov 2018 16:02:25 +
Subject: [PATCH 6/7] [TESTSUITE] Fix tests requiring float printf support when
GCC was configured with --enable-newlib-nano-formatted-io
2018-11-14 Jozef Lawrynowicz
gcc/testsuite/Chang
On Thu, 15 Nov 2018 10:36:57 +0100
Andreas Schwab wrote:
> On Nov 14 2018, Jozef Lawrynowicz wrote:
>
> > The timeout as set in the dejagnu configuration for msp430
> > ([dejagnu.git]/baseboards/msp430-sim.exp) is 30, which is rarely
> > hit.
>
> I don't th
Patch 3 extends the regex in some tests which scan the assembler output for
"nop". On MSP430, the nop instruction is an uppercase "NOP".
>From 6ad3780262543c5237e939ac14ac6294a2adc77b Mon Sep 17 00:00:00 2001
From: Jozef Lawrynowicz
Date: Tue, 6 Nov 2018 12:59:58 +0
rom: Jozef Lawrynowicz
Date: Tue, 6 Nov 2018 12:50:01 +
Subject: [PATCH 4/4] [TESTSUITE] size of short == size of int
2018-11-08 Jozef Lawrynowicz
gcc/testsuite/ChangeLog:
* gcc.dg/attr-alloc_size-10.c: Fix calculation of USHRT_MAX to prevent
integer overflow when sizeof(short) == siz
I've committed some "obvious" changes to GCC tests that fix failures when
running the GCC testsuite for msp430-elf.
Patch 1 adds a couple of new regexp strings to gcc-dg-prune to catch messages
emitted by GNU ld, when the size of an output section is too large for a memory
region, or the memory
Patch 2 skips tests expecting NULL pointer checks to be deleted
with the -fdelete-null-pointer-checks flag, for targets which ignore this flag.
>From 55b405a4d2c694ffdbcbd6808e139d88cb2d2447 Mon Sep 17 00:00:00 2001
From: Jozef Lawrynowicz
Date: Tue, 6 Nov 2018 12:59:33 +
Subject: [PATC
Patch 1 adds a couple of new regexp strings to gcc-dg-prune to catch messages
emitted by GNU ld, when the size of an output section is too large for a memory
region, or the memory region overflows.
>From af810d86c47092e56590f5c13d0633c490f53c9d Mon Sep 17 00:00:00 2001
From: Jozef Lawrynow
On 14/11/2018 18:50, Paul Koning wrote:
On Nov 14, 2018, at 1:00 PM, Jozef Lawrynowicz wrote:
On 14/11/2018 16:54, Andreas Schwab wrote:
On Nov 14 2018, Jozef Lawrynowicz wrote:
diff --git a/gcc/testsuite/c-c++-common/torture/builtin-arith-overflow-10.c
b/gcc/testsuite/c-c++-common
On 14/11/2018 16:54, Andreas Schwab wrote:
On Nov 14 2018, Jozef Lawrynowicz wrote:
diff --git a/gcc/testsuite/c-c++-common/torture/builtin-arith-overflow-10.c
b/gcc/testsuite/c-c++-common/torture/builtin-arith-overflow-10.c
index 6b1c427..71d24ce 100644
--- a/gcc/testsuite/c-c++-common
ping for these patches
[PATCH 1/4] [MSP430] Consolidate hard-coded MCU data
https://gcc.gnu.org/ml/gcc-patches/2018-06/msg01673.html
[PATCH 2/4] [MSP430] Update hard-coded MCU data
https://gcc.gnu.org/ml/gcc-patches/2018-06/msg01674.html
[PATCH 3/4] [MSP430] Search for MCU data file on include
:00 2001
From: Jozef Lawrynowicz
Date: Sat, 10 Nov 2018 16:08:44 +
Subject: [PATCH] [TESTSUITE] Fix tests for msp430-elf large memory model
2018-11-21 Jozef Lawrynowicz
gcc/ChangeLog:
* doc/sourcebuild.texi: Document
check_effective_target_msp430_large_mem.
gcc/testsuite/Change
though __int20 is the underlying type. It is only when the builtin macros
for these types are used does the error occur.
Successfully regtested x86_64-pc-linux-gnu and msp430-elf/-mlarge.
Ok for trunk?
>From b940f79fa7c2a76fdda75dae7baf2bd48c72e9fa Mon Sep 17 00:00:00 2001
From: Jozef Lawrynow
this have to wait for GCC10 Stage 1?
>From b44723988dfb0bb9e8c647dd86aeba762ebdf84d Mon Sep 17 00:00:00 2001
From: Jozef Lawrynowicz
Date: Tue, 18 Dec 2018 11:14:35 +
Subject: [PATCH] Check requested alignment in SET_{DECL,TYPE}_ALIGN is
pow2_or_zerop before aligning on targets with partial
to trunk.
>From 18eb3191fee5f7cc8288cfd88a0b76259b8b547c Mon Sep 17 00:00:00 2001
From: Jozef Lawrynowicz
Date: Sat, 29 Dec 2018 16:27:49 +
Subject: [PATCH] [MSP430] Warn that the critical function attribute has no
effect on interrupt functions
2018-12-29 Jozef Lawrynowicz
gcc
On Fri, 11 Jan 2019 13:00:22 -0700
Jeff Law wrote:
> On 12/30/18 4:51 AM, Jozef Lawrynowicz wrote:
> >
> > The attached patch adds an assertion that SET_{DECL,TYPE}_ALIGN is called
> > with
> > a value which is a power of 2, or 0, for targets which support a partia
On Tue, 18 Dec 2018 03:08:51 -0600
Segher Boessenkool wrote:
> Hi!
>
> On Fri, Dec 14, 2018 at 03:22:13PM +0000, Jozef Lawrynowicz wrote:
> > 2018-12-14 Jozef Lawrynowicz
> >
> > gcc/ChangeLog:
> > * combine.c (update_rsp_from_reg_equal
is always 16 for MSP430, the attached patch (committed to
trunk) sets TARGET_VTABLE_ENTRY_ALIGN to 16 for MSP430. This fixes the above
ICE.
Index: gcc/ChangeLog
===
--- gcc/ChangeLog (revision 267228)
+++ gcc/ChangeLog (revision 267229
0 2001
From: Jozef Lawrynowicz
Date: Tue, 27 Nov 2018 19:03:53 +
Subject: [PATCH] Use last_set_nonzero_bits for a REG when REG mode is
MODE_PARTIAL_INT
2018-12-12 Jozef Lawrynowicz
gcc/ChangeLog:
* combine.c (reg_nonzero_bits_for_combine): Use last_set_nonzero_bits
for a reg if the current mod
parity with how last_set_nonzero_bits are set
in record_value_for_reg.
I've regtested the attached patch for msp430-elf, currently bootstrapping and
testing on x86_64-pc-linux-gnu.
Is this ok for trunk if bootstrap and regtest for x86_64-pc-linux-gnu is
successful?
Jozef
2018-12-14 Jozef Lawrynow
On Tue, 27 Nov 2018 10:49:56 -0800
Mike Stump wrote:
> On Nov 26, 2018, at 3:07 PM, Jozef Lawrynowicz
> wrote:
> >
> > It appears you can actually add __extension__ everywhere (that I tried),
> > except
> > for the argument types in the declaration
On Wed, 14 Nov 2018 15:41:00 +
Jozef Lawrynowicz wrote:
> Patch 7 fixes tests for msp430-elf in the large memory model.
Added missing documentation for new check_effective target procs in attached
patch.
>From 4cfb2ecd0e0580f69790fadd68b77e8a82992ef4 Mon Sep 17 00:00:00 2001
From:
On Wed, 14 Nov 2018 15:41:00 +
Jozef Lawrynowicz wrote:
> Patch 6 fixes tests expecting printf float support for targets which have been
> configured with "newlib-nano-formatted-io". When newlib is configured in this
> way, float printf is enabled at build time by regist
On Wed, 14 Nov 2018 15:41:00 +
Jozef Lawrynowicz wrote:
> Patch 3 sets up require-effective-target directives for tests which
> require the compilation of large arrays.
> Targets which have 16-bit or 20-bit size_t fail to compile tests with large
> arrays designed to test 32-b
1 - 100 of 287 matches
Mail list logo