On Mon, 13 Feb 2017, Jeff Law wrote:
> On 02/10/2017 05:24 AM, Richard Biener wrote:
> >
> > It turns out the SSA var defs/uses generated by the gimplifier can break
> > apart in a way no longer satisfying the dominance requirement of SSA
> > uses vs. their defs by means of CFG construction addin
Hi maintainers,
Please find the below patch which changes the code alignment values for znver1.
Bootstrap and regression test passed on x86_64.
OK to apply?
Thanks,
Amit Pawar
diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index 2561d53..a5b0159 100644
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1
On Mon, Feb 13, 2017 at 04:53:19PM -0700, Jeff Law wrote:
> > dirtype is one of the standard {un,}signed {char,short,int,long,long long}
> > types, all of them have 0 in their ranges.
> > For VR_RANGE we almost always set res.knownrange to true:
> > /* Set KNOWNRANGE if the argument is in
This is the first patch in the series with Richi's comments from last
week addressed. #2, #3 and #4 were unchanged.
Richi asked for the EXACT_DIV_EXPR handling in
extract_range_from_binary_exit_1 to move out one IF conditional nesting
level.
Richi noted that the use of symbolic_range_base
So imagine we have two allocnos related by a copy chain (two operand
architecture).
(gdb) p *cp->first
$11 = {num = 9, regno = 33, mode = DImode, wmode = DImode, aclass =
GENERAL_REGS, dont_reassign_p = 0,
bad_spill_p = 0, assigned_p = 1, conflict_vec_p = 0, hard_regno = -1,
next_regno_all
On 02/11/2017 09:18 PM, Sandra Loosemore wrote:
I noticed a bunch of copy-editing issues in the "ARC Options" section of
invoke.texi. I'm willing to take a stab at fixing them, but I need some
technical assistance since I'm not familiar with the details of this
architecture myself.
Here's the
On 02/09/2017 11:08 AM, Aldy Hernandez wrote:
For those of you not following the PR, this is a re-post of a patch that
was approved in some form a year+ ago, but was reverted because it
caused an undiagnosed bootstrap problem on AIX:
https://gcc.gnu.org/ml/gcc-patches/2016-02/msg00421.html
Anno
On 02/04/2017 01:07 AM, Jakub Jelinek wrote:
On Fri, Feb 03, 2017 at 05:39:21PM +0100, Jakub Jelinek wrote:
Say in the http://gcc.gnu.org/ml/gcc-patches/2017-02/msg00234.html
patch, you would with my patch need just the tree_digits part,
and then the very last hunk in gimple-ssa-sprintf.c (with
On 02/10/2017 10:55 AM, Martin Sebor wrote:
The recent Fedora mass rebuild revealed that the Wformat-truncation=2
checker is still a bit too aggressive and complains about potentially
unbounded strings causing subsequent directives t exceed the INT_MAX
limit. (It's unclear how the build ended up
On 02/09/2017 07:23 AM, Gerald Pfeifer wrote:
On Thu, 9 Feb 2017, Gerald Pfeifer wrote:
As Jakub also pointed out, there are various places where our
BUGURL is defined (not just used).
So, this one I found particularly interesting.
The same URL is used four times in the same file, which begs
On 02/07/2017 01:39 AM, Richard Biener wrote:
On Mon, Feb 6, 2017 at 10:57 PM, Jeff Law wrote:
On 02/06/2017 08:33 AM, Richard Biener wrote:
ah, indeed vr0type is VR_ANTI_RANGE and yes we have the case of a
range with an anti-range "inside". This also covers [-1,1] v
~[0,0] where you choose
On 02/10/2017 05:24 AM, Richard Biener wrote:
It turns out the SSA var defs/uses generated by the gimplifier can break
apart in a way no longer satisfying the dominance requirement of SSA
uses vs. their defs by means of CFG construction adding abnormal edges
for stuff like setjmp (but also non-l
On 02/10/2017 12:58 PM, Jakub Jelinek wrote:
Hi!
Apparently on s390x with -march=z10 and above at -O2, some of the _Decimal32
computations are performed in _Decimal64 precision. As the test intent
is to test the diagnostics on cast from floating point types to integral
types, the values we want
Here build_data_member_initialization got confused by the
initialization of a field of local variable f and thought it was
initializing a field of S; when we then went looking for that field in
S, we didn't find it, and crashed. But if the target of an
initialization is a member of a VAR_DECL, it
This fixes float128 on BE and on 32-bit.
The configure tests need to use -mabi=altivec for 32-bit, since it is
not the default there. That also enables the "vector" keyword, used by
the tests. To do this it temporarily adds a few flags to the CFLAGS
variable.
It also fixes a syntax error in the
On 02/13/2017 12:42 PM, Jakub Jelinek wrote:
Hi!
While looking at PR79475 (already fixed), I wrote a small scriptlet
#!/bin/awk -f
/^[[:blank:]]*"[^[:blank:]]/ {
if (last)
{
print last
print
}
}
{
last = ""
}
/[^[:blank:]]"[[:blank:]]*\\?$/ {
if ($0 ~ /\\[tnv]"[[:blank:
On 02/13/2017 12:49 PM, Jakub Jelinek wrote:
Hi!
Another case of missing whitespace when string literals are split
across multiple lines, I believe we should emit a space here
for nicer formatting.
Ok for trunk?
2017-02-13 Jakub Jelinek
* config/nvptx/mkoffload.c (process): Add spa
On 02/13/2017 12:50 PM, Jakub Jelinek wrote:
Hi!
And lastly this patch fixes 3 diagnostics issues found by that script
in the C++ FE. Bootstrapped/regtested on x86_64-linux and i686-linux,
ok for trunk?
2017-02-13 Jakub Jelinek
* init.c (warn_placement_new_too_small): Add missing s
On 02/13/2017 01:11 PM, Martin Sebor wrote:
When the size of the destination in a call to snprintf is in
a range, at level 1 -Wformat-truncation uses the upper bound
as the size while the stricter level 2 uses the lower bound.
However, when the lower bound is zero treating it the same as
a consta
On 02/12/2017 01:27 AM, Gerald Pfeifer wrote:
On Tue, 7 Feb 2017, Martin Sebor wrote:
The attached documentation-only patch clarifies the description
of the -dM option to mention that __FILE__ (and other predefined
macros) do no appear on the list generated by the option.
+The predefined macr
This fixes many sanitizer problems with -m32.
This patch should go via LLVM, it's just FYI for here for now.
Segher
---
libsanitizer/sanitizer_common/sanitizer_stacktrace.cc | 13 ++---
1 file changed, 10 insertions(+), 3 deletions(-)
diff --git a/libsanitizer/sanitizer_common/saniti
Now with the patch attached.
2017-02-13 13:35 GMT-07:00 Alessandro Fanfarillo :
> Thanks Jerry. That test case is supposed only to be compiled (it never
> runs). Anyway, the attached patch has been modified according to your
> suggestion.
>
> Patch built and regtested on x86_64-pc-linux-gnu.
>
> 2
Thanks Jerry. That test case is supposed only to be compiled (it never
runs). Anyway, the attached patch has been modified according to your
suggestion.
Patch built and regtested on x86_64-pc-linux-gnu.
2017-02-12 10:24 GMT-07:00 Jerry DeLisle :
> On 02/11/2017 03:02 PM, Alessandro Fanfarillo wro
Changes from previous version:
- The split-stack are is now allocated before the thread pointer
(instead of tcbhead_t which is positioned after it) as decribed
in glibc patch [1]. It has the advantage to not require linker
changes to take in consideration the new tcbhead_t size and
When the size of the destination in a call to snprintf is in
a range, at level 1 -Wformat-truncation uses the upper bound
as the size while the stricter level 2 uses the lower bound.
However, when the lower bound is zero treating it the same as
a constant zero and optimizing the call into a consta
Hi!
And lastly this patch fixes 3 diagnostics issues found by that script
in the C++ FE. Bootstrapped/regtested on x86_64-linux and i686-linux,
ok for trunk?
2017-02-13 Jakub Jelinek
* init.c (warn_placement_new_too_small): Add missing space in
diagnostics.
* parser.c
On Mon, Feb 13, 2017 at 8:45 PM, Jakub Jelinek wrote:
> Hi!
>
> Unlike the previous patch that is mainly about diagnostics or dump
> text, this one is something that could potentially crash the compiler,
> the missing , in between means MOD4_SSE_REGS class has
> MOD4_SSE_REGSALL_REGS name and ALL_
On Mon, 2017-02-13 at 20:47 +0100, Jakub Jelinek wrote:
> Hi!
>
> Not really sure about this, but I'd expect if you meant to write
> "foofood",
> you'd have written it that way and not
> "foo"
> "food",
> Passes -fself-test either way, bootstrapped/regtested on x86_64-linux
> and
> i686-linu
Hi!
Another case of missing whitespace when string literals are split
across multiple lines, I believe we should emit a space here
for nicer formatting.
Ok for trunk?
2017-02-13 Jakub Jelinek
* config/nvptx/mkoffload.c (process): Add space in between
, and %d.
--- gcc/config
Hi!
Not really sure about this, but I'd expect if you meant to write
"foofood",
you'd have written it that way and not
"foo"
"food",
Passes -fself-test either way, bootstrapped/regtested on x86_64-linux and
i686-linux, ok for trunk?
2017-02-13 Jakub Jelinek
* spellcheck.c (test_
Hi!
Unlike the previous patch that is mainly about diagnostics or dump
text, this one is something that could potentially crash the compiler,
the missing , in between means MOD4_SSE_REGS class has
MOD4_SSE_REGSALL_REGS name and ALL_REGS class will have NULL or whatever.
Bootstrapped/regtested on
Hi!
While looking at PR79475 (already fixed), I wrote a small scriptlet
#!/bin/awk -f
/^[[:blank:]]*"[^[:blank:]]/ {
if (last)
{
print last
print
}
}
{
last = ""
}
/[^[:blank:]]"[[:blank:]]*\\?$/ {
if ($0 ~ /\\[tnv]"[[:blank:]]*\\?$/)
last = ""
else
last = $0
}
On Mon, Feb 13, 2017 at 12:24:08PM +0100, Richard Biener wrote:
> You'd of course allocate it on the stack. But yeah, sth like your patch
> works for me.
Now bootstrapped/regtested successfully on x86_64-linux and i686-linux.
So is this ok for trunk and perhaps we can add new APIs later?
> > 201
Hi!
As mentioned in the PR, ICC as well as clang have these non-masked
gather prefetch intrinsics in addition to masked (and for scatter
even GCC has both masked and non-masked), but GCC does not (the
SDM actually doesn't mention those, only those for scatters).
The following patch implements tho
On 02/13/2017 12:28 PM, Jakub Jelinek wrote:
The reason for that VOID_TYPE_P stuff in COND_EXPR handling is not
that stabilize_expr doesn't like it, but to avoid warning twice.
If I replace all 3 VOID_TYPE_P tests (with the patch) in
cp_build_modify_expr with 0 && VOID_TYPE_P, the above testcas
This patch to libgo fixes some tests on s390x that rely on assembler
code that is not (yet) implemented for gccgo. The tests are simply
marked to be ignored. This fixes GCC PR 79443. Bootstrapped and
tested on x86_64-pc-linux-gnu and (by Dominik Vogt) on s390x.
Committed to mainline.
Ian
Index
On Mon, Feb 13, 2017 at 05:44:54PM +0100, Jakub Jelinek wrote:
> On Mon, Feb 13, 2017 at 11:41:48AM -0500, Nathan Sidwell wrote:
> > On 02/13/2017 10:46 AM, Jakub Jelinek wrote:
> > > Hi!
> > >
> > > I'd like to ping a couple of patches:
> > >
> > > - C++ P1 PR79232 - ICEs and wrong-code with COM
OK.
On Mon, Feb 13, 2017 at 12:04 PM, Nathan Sidwell wrote:
> On 02/06/2017 02:19 PM, Jason Merrill wrote:
>
>>> AFAICT we cannot easily assert the condition anymore -- C++11 added the
>>> ability for instantiations involving local types.
>>
>>
>> That doesn't mean they have linkage, though; this
The testcase should xfail when compiling for a 64-bit target, not when
the default target is 64-bit.
Tested on powerpc-linux {-m32,-m64}, committing to trunk.
Segher
2017-02-13 Segher Boessenkool
gcc/testsuite/
* gcc.dg/tree-ssa/ssa-dom-cse-2.c: Do not xfail powerpc64*-*-*.
On 02/13/2017 06:34 AM, Nathan Sidwell wrote:
I've applied this patch to sort the other branch lists in svn.html. I also
added an index and split
the inactive branch list into merged and plain inactive.
Attention branch maintainers: Please check whether I've incorrectly put a
merged branch o
This patch does the followings:
* Adjusts the default num_gangs to utilize more of GPU hardware.
* Teach libgomp to emit a diagnostic when num_workers isn't supported.
According to the confusing CUDA literature, it appears that the previous
num_gangs wasn't fully utilizing the GPU hardware. The
On 02/06/2017 02:19 PM, Jason Merrill wrote:
AFAICT we cannot easily assert the condition anymore -- C++11 added the
ability for instantiations involving local types.
That doesn't mean they have linkage, though; this type isn't subject
to the ODR, so need_assembler_name_p should be false.
I n
On 02/13/2017 09:15 AM, Marc Glisse wrote:
On Mon, 13 Feb 2017, Jeff Law wrote:
On 02/12/2017 12:13 AM, Marc Glisse wrote:
On Tue, 7 Feb 2017, Jeff Law wrote:
* tree-vrp.c (extract_range_from_binary_expr_1): For EXACT_DIV_EXPR,
if the numerator has the range ~[0,0] make the resultant range ~
On Mon, Feb 13, 2017 at 4:51 AM, Jonathan Wakely wrote:
> On 13/02/17 13:09 +0100, Jakub Jelinek wrote:
>>
>> Hi!
>>
>> This patch updates baseline_symbols.txt mostly from our latest rpm builds,
>> x86_64 and i686 have been also compared to my local bootstrap abi lists
>> and s390 (31-bit) comes f
On 02/13/2017 10:46 AM, Jakub Jelinek wrote:
Hi!
I'd like to ping a couple of patches:
- C++ P1 PR79232 - ICEs and wrong-code with COMPOUND_EXPR on lhs of assignment
http://gcc.gnu.org/ml/gcc-patches/2017-01/msg02341.html
What puzzles me about (and may be an existing orthogonal issue), is t
On Mon, Feb 13, 2017 at 11:41:48AM -0500, Nathan Sidwell wrote:
> On 02/13/2017 10:46 AM, Jakub Jelinek wrote:
> > Hi!
> >
> > I'd like to ping a couple of patches:
> >
> > - C++ P1 PR79232 - ICEs and wrong-code with COMPOUND_EXPR on lhs of
> > assignment
> > http://gcc.gnu.org/ml/gcc-patches/
These are a runtime testcases so they should test p8vector_hw instead of
powerpc_p8vector_ok, or they will fail with an illegal instruction on
older processors.
Also they run on any PowerPC, not with just those compilers that were
configured to default to 64-bit targets.
Tested on powerpc64-linux
On Mon, 13 Feb 2017, Jeff Law wrote:
On 02/12/2017 12:13 AM, Marc Glisse wrote:
On Tue, 7 Feb 2017, Jeff Law wrote:
* tree-vrp.c (extract_range_from_binary_expr_1): For EXACT_DIV_EXPR,
if the numerator has the range ~[0,0] make the resultant range ~[0,0].
If I understand correctly, for x /[
On 02/12/2017 12:13 AM, Marc Glisse wrote:
On Tue, 7 Feb 2017, Jeff Law wrote:
* tree-vrp.c (extract_range_from_binary_expr_1): For EXACT_DIV_EXPR,
if the numerator has the range ~[0,0] make the resultant range ~[0,0].
If I understand correctly, for x /[ex] 4 with x!=0, we currently split
~[0
On 13/02/17 15:53, Kyrill Tkachov wrote:
Hi all,
We recently (well, within the last year or two) introduced a general function
to detect MEM sub-rtxes in rtlanal.c: contains_mem_rtx_p.
We can use that in aarch64.c and remove the custom has_memory_op that is
defined in the same way (except tha
Hi all,
We recently (well, within the last year or two) introduced a general function
to detect MEM sub-rtxes in rtlanal.c: contains_mem_rtx_p.
We can use that in aarch64.c and remove the custom has_memory_op that is
defined in the same way (except that it takes an rtx_insn * instead of an rtx)
Hi!
I'd like to ping a couple of patches:
- C++ P1 PR79232 - ICEs and wrong-code with COMPOUND_EXPR on lhs of assignment
http://gcc.gnu.org/ml/gcc-patches/2017-01/msg02341.html
- C++ P1 PR79288 - wrong default TLS model for __thread static data members
http://gcc.gnu.org/ml/gcc-patches/2017-
Hi Jakub,
On Fri, Feb 10, 2017 at 08:50:36PM +0100, Jakub Jelinek wrote:
> On the following testcases combiner during notes distribution sees a
> REG_DEAD note and decides to remove the setter thereof. That register
> has remembered a last value on that insn though, and it is a pseudo set
> multi
On 07/02/17 14:04, Kyrill Tkachov wrote:
> Hi all,
>
> Currently, -mprint-tune-info gives an assembly file that cannot be
> assembled because the branch cost values
> are not properly commented. For example:
> @.tune parameters
> @constant_limit:1
>
On 02/12/2017 05:58 AM, Gerald Pfeifer wrote:
On Mon, 6 Feb 2017, Nathan Sidwell wrote:
Are you planning to add this to svn.html
Ah, thanks for the reminder.
And here's the patch I committed to document the branch.
nathan
--
Nathan Sidwell
? htdocs/.#svn.html.1.208
Index: htdocs/svn.html
==
On 02/13/2017 09:34 AM, Nathan Sidwell wrote:
I've applied this patch to sort the other branch lists in svn.html. I
also added an index and split the inactive branch list into merged and
plain inactive.
I think these /p tags are needed. At least that's my interpretation of
the validator erro
I've applied this patch to sort the other branch lists in svn.html. I
also added an index and split the inactive branch list into merged and
plain inactive.
Attention branch maintainers: Please check whether I've incorrectly
put a merged branch on the inactive list.
nathan
--
Nathan Sidwel
On 13/02/17 21:40 +0800, Tim Song wrote:
On Tue, Jan 31, 2017 at 1:54 AM, Jonathan Wakely wrote:
after including unrelated headers such as , , , and
or ?
Thanks, I think my fingers got confused by "mutex" and "regex" and
started ending everythign with -ex.
Fixed with this patch, commit
On 13/02/17 12:57, Prathamesh Kulkarni wrote:
> Hi,
> As mentioned in PR, the attached patch sets source range when parsing ssa-name
> in c_parser_gimple_postfix_expression which avoids uninitialized use.
> Is it OK to commit after bootstrap+test ?
Ok.
Richard.
> Thanks,
> Prathamesh
>
On Tue, Jan 31, 2017 at 1:54 AM, Jonathan Wakely wrote:
> after including unrelated headers such as , , , and
>
or ?
On 12/02/17 15:47 +0100, Gerald Pfeifer wrote:
It appears we have been using various ways to refer to bits of Boost
documentation, and I suggest to standardize this a bit per the patch
below.
http://www.boost.org/libs/ seems to be the shortest and
simplest form doing to.
Thoughts?
Works for m
This is a similar bug to the is_callable assertions I fixed in
shared_ptr the other day: it needs to use the correct value category
in the result_of type. This is also a regression, in code that has
been refactored on trunk.
PR libstdc++/79486
* include/std/future (__future_base::
On 02/13/2017 02:06 PM, Martin Liška wrote:
On 02/13/2017 01:58 PM, Bernd Schmidt wrote:
On 02/13/2017 11:15 AM, Martin Liška wrote:
In order to not cause a stack overflow, lets use a vector allocated on heap
instead of
the one created by XALLOCVEC.
Patch can bootstrap on ppc64le-redhat-linux
On 02/13/2017 01:58 PM, Bernd Schmidt wrote:
> On 02/13/2017 11:15 AM, Martin Liška wrote:
>> In order to not cause a stack overflow, lets use a vector allocated on heap
>> instead of
>> the one created by XALLOCVEC.
>>
>> Patch can bootstrap on ppc64le-redhat-linux and survives regression tests.
On 02/10/2017 08:50 PM, Jakub Jelinek wrote:
2017-02-10 Jakub Jelinek
PR rtl-optimization/79388
PR rtl-optimization/79450
* combine.c (distribute_notes): When removing TEM_INSN for which
corresponding dest has last value recorded, invalidate that last
On 02/11/2017 08:24 AM, Richard Biener wrote:
> On February 11, 2017 12:38:32 AM GMT+01:00, Jakub Jelinek
> wrote:
>> On Fri, Feb 10, 2017 at 04:34:30PM -0700, Jeff Law wrote:
2017-02-10 Richard Biener
config/
* isl.m4: Remove support for ISL 0.14.
* conf
On 02/13/2017 11:15 AM, Martin Liška wrote:
In order to not cause a stack overflow, lets use a vector allocated on heap
instead of
the one created by XALLOCVEC.
Patch can bootstrap on ppc64le-redhat-linux and survives regression tests.
Ok. I'm surprised this is marked as a regression, but it'
On 13/02/17 13:09 +0100, Jakub Jelinek wrote:
Hi!
This patch updates baseline_symbols.txt mostly from our latest rpm builds,
x86_64 and i686 have been also compared to my local bootstrap abi lists
and s390 (31-bit) comes from my bootstrap (and 64-bit s390x compared against
the rpm builds too).
s
Hi!
This patch updates baseline_symbols.txt mostly from our latest rpm builds,
x86_64 and i686 have been also compared to my local bootstrap abi lists
and s390 (31-bit) comes from my bootstrap (and 64-bit s390x compared against
the rpm builds too).
s390{,x}-linux weren't updated the last time (for
Hi,
As mentioned in PR, the attached patch sets source range when parsing ssa-name
in c_parser_gimple_postfix_expression which avoids uninitialized use.
Is it OK to commit after bootstrap+test ?
Thanks,
Prathamesh
2017-02-13 Prathamesh Kulkarni
PR c/79478
* gimple-parser.c (c_p
On Mon, 13 Feb 2017, Jakub Jelinek wrote:
On Mon, Feb 13, 2017 at 09:59:12AM +0100, Richard Biener wrote:
On Sun, 12 Feb 2017, Marc Glisse wrote:
On Sun, 12 Feb 2017, Marc Glisse wrote:
On Tue, 7 Feb 2017, Jakub Jelinek wrote:
* tree-vrp.c (simplify_div_or_mod_using_ranges): If op
On Mon, 13 Feb 2017, Jakub Jelinek wrote:
> On Mon, Feb 13, 2017 at 09:59:12AM +0100, Richard Biener wrote:
> > On Sun, 12 Feb 2017, Marc Glisse wrote:
> >
> > > On Sun, 12 Feb 2017, Marc Glisse wrote:
> > >
> > > > On Tue, 7 Feb 2017, Jakub Jelinek wrote:
> > > >
> > > > > * tree-vrp.c (
On Sun, Feb 12, 2017 at 09:08:42AM +0100, Gerald Pfeifer wrote:
> On Wed, 8 Feb 2017, Marek Polacek wrote:
> > Like this?
>
> As a consequence, the following examples are invalid and G++ will no longer
> -compile them:
> +compile them, because, in the following examples, G++ used to treat
> +this
Hello.
In order to not cause a stack overflow, lets use a vector allocated on heap
instead of
the one created by XALLOCVEC.
Patch can bootstrap on ppc64le-redhat-linux and survives regression tests.
Ready to be installed?
Martin
>From c71fadc2104c729ae5625e06c54239998dd794a5 Mon Sep 17 00:00:00
This patch adds:
// New functions to set/get the current default async queue
void acc_set_default_async (int);
int acc_get_default_async (void);
and _async versions of a few existing API functions:
void acc_copyin_async (void *, size_t, int);
void acc_create_async (void *, size_t, int);
void acc
On Mon, Feb 13, 2017 at 09:59:12AM +0100, Richard Biener wrote:
> On Sun, 12 Feb 2017, Marc Glisse wrote:
>
> > On Sun, 12 Feb 2017, Marc Glisse wrote:
> >
> > > On Tue, 7 Feb 2017, Jakub Jelinek wrote:
> > >
> > > > * tree-vrp.c (simplify_div_or_mod_using_ranges): If op1 is not
> > > >
On Sun, 12 Feb 2017, Marc Glisse wrote:
> On Sun, 12 Feb 2017, Marc Glisse wrote:
>
> > On Tue, 7 Feb 2017, Jakub Jelinek wrote:
> >
> > > * tree-vrp.c (simplify_div_or_mod_using_ranges): If op1 is not
> > > constant, but SSA_NAME with a known integer range, use the minimum
> > > of that r
77 matches
Mail list logo
