I am currently testing the following patch that handle both modules and
submodules. It is a little bit clumsy and may not handle all the possible
syntax variants. Any comment welcomed!-) Testing in progress.
Dominique
--- ../_clean/gcc/testsuite/lib/fortran-modules.exp 2017-01-01
17:38:58.
2017-04-15 Uros Bizjak
* gcc.dg/pr54669.c: Fix dg-do directive.
* gcc.dg/pr78582.c: Ditto.
* gcc.dg/pr80020.c: Ditto.
* gcc.dg/torture/pr57993-2.cpp: Ditto.
* gcc.dg/tree-ssa/builtin-sprintf-3.c: Ditto.
* gcc.dg/tree-ssa/builtin-sprintf-4.c: Ditto.
* gcc.dg/tree-ssa/
Committed as revision r246940.
Dominique
> Le 15 avr. 2017 à 16:56, Janus Weil a écrit :
>
> 2017-04-15 16:46 GMT+02:00 Dominique d'Humières :
>> I am planning to commit as obvious the following changes
>
> Sure! But ...
>
>
>> --- ../_clean/gcc/testsuite/gfortran.dg/deferred_character_3.f90
2017-04-15 17:54 GMT+02:00 Dominique d'Humières :
>>> This is indeed doable, but before I’ld like to improve the module cleanup
>>> with the following patch
>>
>> Yes, looks very useful to me (makes the regexps much more compact &
>> readable). In addition, couldn't one use \s for whitespace inste
> Le 15 avr. 2017 à 17:13, Janus Weil a écrit :
>
> 2017-04-15 15:57 GMT+02:00 Dominique d'Humières :
>>
>>> Le 15 avr. 2017 à 13:00, Janus Weil a écrit :
>>>
>>> Hi Dominique,
>>>
>>> if I'm not mistaken, the cleanup of module file in the testsuite is
>>> done automatically by now, right? C
On Apr 15, 2017, at 1:07 AM, Tom de Vries wrote:
> I've attached two patches:
>
> - second patch is the result of running the script.
> Second patch OK for stage4/stage1 trunk?
Ok.
> [ I'm not sure if the first patch is useful enough to commit to contrib. ]
Once the script it run, we shouldn'
Similar to the patch for decoding numbers, puts the handling of
character decoding into a designated function with the same style
caller interface. Removes one nested level and decoding logic from
`dlang_parse_string'.
Added some more tests, which brings overall coverage of this code to
all but 3
This fixes two main problems found in the use of strtol(). First that
it returns `0' if nothing is decoded, and none of the callers checked
whether nothing was consumed. Second that it just returns `LONG_MAX'
on overflow. Rather than updating each individual call site, have
solved [1] by moving
This patch removes `dlang_parse_symbol', and replaces it with
`dlang_parse_qualified' and `dlang_parse_mangle'. All callers have
been updated to reflect as to whether we expect either a `MangleName'
or `QualifiedName' to be the next token we encounter, which matches
many clarifications that have b
This updates the implementation to reflect a part of the D ABI spec
that has been removed. There should never be a bare integer value
encoded into a template argument list. Integers are always prefixed
by `i' if they are positive or `N' if they are negative.
Have verified this indeed is the case
This implements another previously undocumented part of the D ABI
spec, where symbols with no name are always encoded into the mangled
name.
SymbolName:
LName
TemplateInstanceName
0 // anonymous symbols
This has never really been a problem, as strtol() kind
This implements a previously an undocumented part of the D ABI spec,
where symbols instantiated inside a template constraint are given a
different prefix. In practise however this should never be
encountered, as such instantiations are normally considered
speculative, and so never make it to objec
The next version of D adds a new `scope' function attribute. This
adds support for demangling them.
---
commit 15a0592cf6403fccbf43f3c7dc44f7d22c0f3dfa
Author: Iain Buclaw
Date: Sat Apr 15 11:15:41 2017 +0200
libiberty/ChangeLog:
2017-04-15 Iain Buclaw
* d-demangle.c
Hi,
This patch series includes a new addition to the current iteration of
the D language, plus many fixes surrounding the clarification of
certain parts of the D ABI specification.
---
Iain Buclaw (7):
[D] libiberty: Add support for demangling scope attributes.
[D] libiberty: Add support for
2017-04-15 15:57 GMT+02:00 Dominique d'Humières :
>
>> Le 15 avr. 2017 à 13:00, Janus Weil a écrit :
>>
>> Hi Dominique,
>>
>> if I'm not mistaken, the cleanup of module file in the testsuite is
>> done automatically by now, right? Couldn't one do the same also for
>> submodules?
>>
>> Cheers,
>>
> Le 15 avr. 2017 à 16:56, Janus Weil a écrit :
>
> 2017-04-15 16:46 GMT+02:00 Dominique d'Humières :
>> I am planning to commit as obvious the following changes
>
> Sure! But ...
>
>
>> --- ../_clean/gcc/testsuite/gfortran.dg/deferred_character_3.f90
>> 2015-11-15 15:12:11.0
2017-04-15 16:46 GMT+02:00 Dominique d'Humières :
> I am planning to commit as obvious the following changes
Sure! But ...
> --- ../_clean/gcc/testsuite/gfortran.dg/deferred_character_3.f90
> 2015-11-15 15:12:11.0 +0100
> +++ gcc/testsuite/gfortran.dg/deferred_character_3.f90 20
I am planning to commit as obvious the following changes
--- ../_clean/gcc/testsuite/gfortran.dg/deferred_character_3.f90
2015-11-15 15:12:11.0 +0100
+++ gcc/testsuite/gfortran.dg/deferred_character_3.f90 2017-04-15
11:43:05.0 +0200
@@ -1,4 +1,4 @@
-! {dg_do run }
+! { dg
> Le 15 avr. 2017 à 13:00, Janus Weil a écrit :
>
> Hi Dominique,
>
> if I'm not mistaken, the cleanup of module file in the testsuite is
> done automatically by now, right? Couldn't one do the same also for
> submodules?
>
> Cheers,
> Janus
>
This is indeed doable, but before I’ld like to i
Hi Dominique,
if I'm not mistaken, the cleanup of module file in the testsuite is
done automatically by now, right? Couldn't one do the same also for
submodules?
Cheers,
Janus
2017-04-15 10:34 GMT+02:00 Dominique d'Humières :
> Hi!
>
> Unless someone objects, I am planning to commit the follow
Hi!
Unless someone objects, I am planning to commit the following cleanup
--- ../_clean/gcc/testsuite/gfortran.dg/submodule_17.f082016-08-24
21:57:16.0 +0200
+++ gcc/testsuite/gfortran.dg/submodule_17.f08 2017-04-15 10:19:32.0
+0200
@@ -25,3 +25,4 @@ end submodule
us
On 03/29/2017 12:23 AM, Jakub Jelinek wrote:
On Tue, Mar 28, 2017 at 08:27:54AM +0200, Tom de Vries wrote:
this patch fixes testsuite PR80220 - "relative line numbers don't work when
put between braces".
What is the advantage of putting the line numbers between braces?
I don't know of any ad
22 matches
Mail list logo