On Mon, 20 Jun 2016, Gerald Pfeifer wrote:
> I know a short version of this was applied, but am wondering
> whether to retain the example (and a note on -flifetime-dse=1),
> both per the discussion in February?
>
> Want to make those enhancements?
And here is one small change I just applied...
G
Hi Martin,
On Wed, 17 Feb 2016, Martin Liška wrote:
> On 02/17/2016 03:23 PM, Jakub Jelinek wrote:
>> "has been" looks weird. I'd say that the C++ compiler is now more
>> aggressive...
> Sending v3.
I know a short version of this was applied, but am wondering
whether to retain the example (and a
On Thu, 25 Feb 2016, Martin Liška wrote:
> That's a suggestion for changes.html.
>
> Ready to be installed?
Works for me, Martin, but please give Jason a day or two to comment.
Thanks,
Gerald
On 02/19/2016 05:52 AM, Jan Hubicka wrote:
> Hi,
> thank you for working this out and writting summary. I think in a shorter
> form this would make
> excellent entry for changes.html, too. We tell about the new feature and
> warn users about fallout
> that is always good.
Good idea.
That's a s
On 2016.02.25 at 11:07 +0100, Markus Trippelsdorf wrote:
> On 2016.02.25 at 11:01 +0100, Martin Liška wrote:
> > On 02/17/2016 04:01 PM, Martin Liška wrote:
> > > On 02/17/2016 03:23 PM, Jakub Jelinek wrote:
> > >> "has been" looks weird. I'd say that the C++ compiler is now more
> > >> aggressive
On 2016.02.25 at 11:01 +0100, Martin Liška wrote:
> On 02/17/2016 04:01 PM, Martin Liška wrote:
> > On 02/17/2016 03:23 PM, Jakub Jelinek wrote:
> >> "has been" looks weird. I'd say that the C++ compiler is now more
> >> aggressive...
> >>
> I've been thinking if the suggested patch makes sense an
On 02/17/2016 04:01 PM, Martin Liška wrote:
> On 02/17/2016 03:23 PM, Jakub Jelinek wrote:
>> "has been" looks weird. I'd say that the C++ compiler is now more
>> aggressive...
>>
>> Jakub
>
> Sending v3.
>
> M.
>
Hi.
I've been thinking if the suggested patch makes sense any longer after
> Hello.
>
> As I finally hunted issue in Firefox that was responsible for start-up
> segfault, I would like
> to describe a new behavior of the compiler that emits clobbers to class
> constructors (w/ -flifetime-dse).
> As also Richi spotted quite similar issue in openjade package, I think it
On 02/17/2016 03:23 PM, Jakub Jelinek wrote:
> "has been" looks weird. I'd say that the C++ compiler is now more
> aggressive...
>
> Jakub
Sending v3.
M.
Index: htdocs/gcc-6/porting_to.html
===
RCS file: /cvs/gcc/wwwdocs/htdo
On Wed, Feb 17, 2016 at 03:21:07PM +0100, Martin Liška wrote:
> --- htdocs/gcc-6/porting_to.html 14 Feb 2016 13:13:43 - 1.14
> +++ htdocs/gcc-6/porting_to.html 17 Feb 2016 14:20:13 -
> @@ -324,6 +324,52 @@
> -fabi-version or -Wabi option to disable or warn about.
>
>
> +
On 02/16/2016 05:55 PM, Martin Sebor wrote:
> I think the new text deserves a new heading of its own rather than
> being added under the existing "Stricter flexible array member rules."
> (The "Finally..." part changed by the patch still applies to the
> flexible array members.)
>
> Martin
Hi Mar
On 02/16/2016 07:55 AM, Martin Liška wrote:
Hello.
As I finally hunted issue in Firefox that was responsible for start-up
segfault, I would like
to describe a new behavior of the compiler that emits clobbers to class
constructors (w/ -flifetime-dse).
As also Richi spotted quite similar issue i
On 16/02/16 14:55, Martin Liška wrote:
Hello.
As I finally hunted issue in Firefox that was responsible for start-up
segfault, I would like
to describe a new behavior of the compiler that emits clobbers to class
constructors (w/ -flifetime-dse).
As also Richi spotted quite similar issue in op
Hello.
As I finally hunted issue in Firefox that was responsible for start-up
segfault, I would like
to describe a new behavior of the compiler that emits clobbers to class
constructors (w/ -flifetime-dse).
As also Richi spotted quite similar issue in openjade package, I think it worth
for ment
14 matches
Mail list logo
