On 09/16/2017 09:35 AM, Bernhard Reutner-Fischer wrote:
+ * for result-adjusting thinks, the FIXED_OFFSET adjustment is done after
s/think/thunk/
TIA
Good catch, thank you! I just pushed the following obvious change, as
r252904:
Fix a typo in a comment (cgraph.c:cgraph_thunk_info)
On Sun, Sep 17, 2017 at 10:42:01PM +0200, Janus Weil wrote:
>
> attached is a (technically) simple patch that implements the compiler
> flag "-fdefault-real-16" for gfortran.
What about -fdefault-real-10? If you're going to add bloat to the
compiler, then you might as well to it right.
--
Stev
Hi Richard,
On 15 September 2017 at 19:31, Richard Biener
wrote:
> On Fri, Sep 15, 2017 at 3:27 AM, Kugan Vivekanandarajah
> wrote:
>> This patch adds separate params for rtl unroller so that they can be
>> tunned accordingly. Default values I have are based on some testing on
>> aarch64. I am h
Attached is a version of
https://gcc.gnu.org/ml/gcc-patches/2017-05/msg00481.html that contains
a combination of both the fix and the testcase update, as requested in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81794#c2
I had to use a different computer than I usually use to send this
email, as t
On Sun, Sep 17, 2017 at 4:41 PM, Kugan Vivekanandarajah
wrote:
> Hi Andrew,
>
> On 15 September 2017 at 13:36, Andrew Pinski wrote:
>> On Thu, Sep 14, 2017 at 6:33 PM, Kugan Vivekanandarajah
>> wrote:
>>> This patch adds aarch64_loop_unroll_adjust to limit partial unrolling
>>> in rtl based on s
Hi Andrew,
On 15 September 2017 at 13:36, Andrew Pinski wrote:
> On Thu, Sep 14, 2017 at 6:33 PM, Kugan Vivekanandarajah
> wrote:
>> This patch adds aarch64_loop_unroll_adjust to limit partial unrolling
>> in rtl based on strided-loads in loop.
>
> Can you expand on this some more? Like give an
Hello world,
the attached patch implements the out-of-bounds errors for DO loops.
Seeing that we only warn for things like
REAL :: A(2)
A(3) = 42.
I think it is best to have an unconditional warning for
simple cases, and something enabled with -Wextra for stuff
like
REAL A(3)
DO I=1,
On 09/17/2017 10:53 AM, Uros Bizjak wrote:
> OK.
>
> Thanks,
> Uros.
Thanks. I should have posted this Friday when my tests finished, but
I'll be committing with one minor change so tests don't run on m32 or mx32:
--- a/gcc/testsuite/gcc.target/i386/pr82196-1.c
+++ b/gcc/testsuite/gcc.target/i386
Hi Janus,
here is a small patch that enables -Wconversion-extra with -Wextra and
updates the documentation.
I grepped for warn_conversion_extra and found 14 occurrences in the
gfortran source tree.
Are we sure we want to enable each of these warnings with -Wextra?
Regards
Thomas
Hi all,
attached is a (technically) simple patch that implements the compiler
flag "-fdefault-real-16" for gfortran.
I know that there is some opposition against this, but I am proposing
it anyway, because I do think it is useful after all. My reasoning is
as follows:
1) Despite tons of -freal-X
On Sun, Sep 17, 2017 at 05:47:11PM +0200, Uros Bizjak wrote:
> > The postreload change is ok.
>
> The revert is OK even without approval.
Well, it isn't a pure reversion, it is reversion plus addition of
const char *name = LABEL_NAME (label);
PUT_CODE (label, NOTE);
NOTE_KIND (label) = NOTE
On Sun, Sep 17, 2017 at 10:21:23PM +0930, Alan Modra wrote:
> When -fstack-protector-all or -fsanitize=address, rs6000.h sets
> FRAME_GROWS_DOWNWARD. This breaks the assumption in
> rs6000_return_addr that the stack link is at frame_pointer+0.
Well, builtin_return_address(N) already works correct
> This patch adds stack clash protection to the x86 port and provides the
> first set of tests that will be used by the other ports in the future.
>
> Changes since V2:
>
> This uses the new PARAMs to determine if probing is needed and how often
> to probe once probing is needed. New tests were ad
On Thu, Sep 14, 2017 at 1:47 PM, Peryt, Sebastian
wrote:
> Hi,
>
> This patch adds options -march=/-mtune=knm for Knights Mill.
>
> 2017-09-14 Sebastian Peryt
> gcc/
>
> * config.gcc: Support "knm".
> * config/i386/driver-i386.c (host_detect_local_cpu): Detect "knm".
>
On Thu, Sep 14, 2017 at 6:03 AM, Daniel Santos wrote:
> I made a silly mistake in libgcc by testing the cpp macro __AVX__ to
> determine rather to use movaps or vmovaps in the stubs. This resulted
> in the stubs choice of instruction being decided by the machine flags
> when the compiler was buil
And, darn it, I forgot to save cpp.texi, leaving out a couple of tweaks
there.
Here's v3. Sorry about the noise.
Tom
diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index e213db6..362f50e 100644
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,7 @@
+2017-09-16 Tom Tromey
+
+ * doc/cpp.tex
On Wed, Sep 13, 2017 at 12:48 PM, Richard Biener wrote:
> On Wed, 13 Sep 2017, Jakub Jelinek wrote:
>
>> Hi!
>>
>> The testcase below (and others) still ICEs with my PR81766 fix.
>> If there is a cfg cleanup in between ix86_init_pic_reg (during RA)
>> and postreload, the label which my fix moved t
On Mon, Sep 11, 2017 at 1:15 PM, Rainer Orth
wrote:
> The new gcc.target/i386/pr81736-[34].c tests currently FAIL on 32-bit
> Solaris x86. Fixed as suggested by HJ in the PR. Tested with the
> appropriate runtest invocation on i386-pc-solaris2.11,
> x86_64-pc-linux-gnu, and x86_64-apple-darwin11
On Mon, Sep 11, 2017 at 3:57 AM, H.J. Lu wrote:
> preferred_stack_boundary may not be the minimum stack alignment. For
> leaf functions without TLS access, max_used_stack_slot_alignment may be
> smaller. We should update preferred_stack_boundary for leaf functions.
>
> Tested on i686 and x86-64.
Tom> I don't really understand the rationale for why the errors are phrased
Tom> the way they are, but I notice the C errors generally mention C99 and
Tom> the C++ errors generally mention C++11. So, since I didn't have a
Tom> rationale, I copied what is already there. I thought maybe GCC is just
> "Alexander" == Alexander Monakov writes:
Alexander> This hunk reverts CXX17 back to CXX1Z.
Thanks for noticing, I'd written this before Jakub's patch and so the
error came in during the rebase.
Alexander> These two hunks add more duplication in already-duplicated 'if'
statement
Alexander
When -fstack-protector-all or -fsanitize=address, rs6000.h sets
FRAME_GROWS_DOWNWARD. This breaks the assumption in
rs6000_return_addr that the stack link is at frame_pointer+0.
Bootstrapped and regression tested powerpc64le-linux and
powerpc64-linux -m32/-m64. OK?
PR target/81996
Hi, all,
In the nds32 port, most of time we prefer reducing code size.
So we modify the nds32_option_optimization_table[] to apply
-fsched-pressure and -fomit-frame-pointer for specific
optimization level.
Committed as Rev.252876: https://gcc.gnu.org/r252876
gcc/
* common/config/nds32/n
Hi!
On Tue, 24 Jan 2017 15:30:34 -0500, David Malcolm wrote:
> On Tue, 2017-01-24 at 13:52 +0100, Martin Jambor wrote:
> > [...] I have just
> > committed the BRIG FE as revision 244867.
In a build with that enabled, I just happened to "make html" in "gcc/",
and ran into:
[...]
makeinfo
On Sat, 16 Sep 2017, Tom Tromey wrote:
> --- a/gcc/doc/cpp.texi
> +++ b/gcc/doc/cpp.texi
> @@ -1675,20 +1675,27 @@ macro. We could define @code{eprintf} like this,
> instead:
[snip]
> +This formulation looks more descriptive, but historically it was less
> +flexible: you had to supply at least on
Hi, all,
I noticed that some 8-spaces should be replaced with tab character.
Here is a patch to refine formatting and comments in nds32 port.
No functionality changes.
Committed as Rev.252874: http://gcc.gnu.org/r252874
gcc/
* config/nds32/nds32.c: Refine formatting and comments.
Hi,
ping... for the documentation part.
Thanks,
Bernd.
On 09/06/17 17:31, Kyrill Tkachov wrote:
>
> On 06/09/17 14:17, Bernd Edlinger wrote:
>> On 09/06/17 14:51, Richard Earnshaw (lists) wrote:
>>> On 06/09/17 13:44, Bernd Edlinger wrote:
On 09/04/17 21:54, Bernd Edlinger wrote:
> Hi
> On Sep 15, 2017, at 19:37 , Nathan Sidwell wrote:
>
> As I mentioned a few months back, I intended to step down as a vxworks
> maintainer. Olivier is more than capable of looking after the target, plus
> he has hardware.
>
> I've committed this patch.
Thanks for your kind words and for yo
28 matches
Mail list logo