From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: David Malcolm <dmalcolm@redhat.com>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] dumpfile.c: use prefixes other that 'note: ' for MSG_{OPTIMIZED_LOCATIONS|MISSED_OPTIMIZATION}
Date: Thu, 04 Oct 2018 11:34:00 -0000 [thread overview]
Message-ID: <yddpnwq2bkt.fsf@CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <mvm36tp7npj.fsf@linux-m68k.org> (Andreas Schwab's message of "Mon, 01 Oct 2018 16:20:40 +0200")
Hi Andreas,
> On Okt 01 2018, David Malcolm <dmalcolm@redhat.com> wrote:
>
>> Is there a link to the .log files somewhere so I can see the precise
>> messages in question? (e.g. are they all "loop versioned for
>> vectorization to enhance alignment"?).
>
> Yes, they are all the same message.
just for the record: I'm seeing exactly the same on Solaris/SPARC (32
and 64-bit).
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
next prev parent reply other threads:[~2018-10-04 11:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-25 21:55 David Malcolm
2018-09-28 9:44 ` Richard Biener
2018-09-29 23:06 ` Andreas Schwab
2018-10-01 14:20 ` David Malcolm
2018-10-01 14:29 ` Andreas Schwab
2018-10-04 11:34 ` Rainer Orth [this message]
2018-12-05 13:57 ` Rainer Orth
2020-11-06 8:38 ` Thomas Schwinge
2020-11-13 22:06 ` Jeff Law
2020-11-24 9:46 ` Thomas Schwinge
2020-11-06 8:50 ` Thomas Schwinge
2020-11-13 22:06 ` Jeff Law
2020-11-24 9:51 ` Thomas Schwinge
2020-11-06 9:26 ` Add 'dg-note' next to 'dg-optimized', 'dg-missed' (was: [PATCH] dumpfile.c: use prefixes other that 'note: ' for MSG_{OPTIMIZED_LOCATIONS|MISSED_OPTIMIZATION}) Thomas Schwinge
2020-11-24 9:53 ` Thomas Schwinge
2020-11-30 19:28 ` Jeff Law
2021-05-18 10:46 ` Add 'dg-note', 'dg-lto-note' (was: Add 'dg-note' next to 'dg-optimized', 'dg-missed') Thomas Schwinge
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=yddpnwq2bkt.fsf@CeBiTec.Uni-Bielefeld.DE \
--to=ro@cebitec.uni-bielefeld.de \
--cc=dmalcolm@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=schwab@linux-m68k.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).