On Thu, May 18, 2017 at 05:22:50PM -0600, Martin Sebor wrote:
> On 05/17/2017 11:19 PM, Andi Kleen wrote:
> > Marek Polacek writes:
> >
> > > On Wed, May 17, 2017 at 09:13:40AM -0600, Jeff Law wrote:
> > > > On 05/17/2017 04:23 AM, Aldy Hernandez wrote:
> > > > > Hi folks.
> > > > >
> > > > > I'
On 05/17/2017 11:19 PM, Andi Kleen wrote:
Marek Polacek writes:
On Wed, May 17, 2017 at 09:13:40AM -0600, Jeff Law wrote:
On 05/17/2017 04:23 AM, Aldy Hernandez wrote:
Hi folks.
I've been having troubles comparing the results of different test runs
for quite some time, and have finally deci
Snapshot gcc-7-20170518 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/7-20170518/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 7 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-7
On 2017.05.18 at 13:42 -0600, Martin Sebor wrote:
> On 05/18/2017 12:55 PM, Markus Trippelsdorf wrote:
> > On 2017.05.18 at 12:41 -0600, Martin Sebor wrote:
> > > On 05/18/2017 11:59 AM, Jeff Law wrote:
> > > > On 05/18/2017 11:41 AM, Martin Sebor wrote:
> > > > > I just tried to push a change and
On 05/18/2017 12:55 PM, Markus Trippelsdorf wrote:
On 2017.05.18 at 12:41 -0600, Martin Sebor wrote:
On 05/18/2017 11:59 AM, Jeff Law wrote:
On 05/18/2017 11:41 AM, Martin Sebor wrote:
I just tried to push a change and got the error below. git
pull says my tree is up to date. I wonder if it'
On 2017.05.18 at 12:41 -0600, Martin Sebor wrote:
> On 05/18/2017 11:59 AM, Jeff Law wrote:
> > On 05/18/2017 11:41 AM, Martin Sebor wrote:
> > > I just tried to push a change and got the error below. git
> > > pull says my tree is up to date. I wonder if it's caused by
> > > my commit conflictin
On Thu, May 18, 2017 at 2:41 PM, Martin Sebor wrote:
> On 05/18/2017 11:59 AM, Jeff Law wrote:
>>
>> On 05/18/2017 11:41 AM, Martin Sebor wrote:
>>>
>>> I just tried to push a change and got the error below. git
>>> pull says my tree is up to date. I wonder if it's caused by
>>> my commit confli
On 05/18/2017 11:59 AM, Jeff Law wrote:
On 05/18/2017 11:41 AM, Martin Sebor wrote:
I just tried to push a change and got the error below. git
pull says my tree is up to date. I wonder if it's caused by
my commit conflicting with another commit (in this case
r248244) that git-svn doesn't see b
On 05/18/2017 11:41 AM, Martin Sebor wrote:
> I just tried to push a change and got the error below. git
> pull says my tree is up to date. I wonder if it's caused by
> my commit conflicting with another commit (in this case
> r248244) that git-svn doesn't see because it lags behind SVN.
> I brus
I just tried to push a change and got the error below. git
pull says my tree is up to date. I wonder if it's caused by
my commit conflicting with another commit (in this case
r248244) that git-svn doesn't see because it lags behind SVN.
I brushed this (and other strange errors) off before, not
b
Hi,
I have implemented the separate preprocess and compile setup in build2.
For GCC it is using -fdirectives-only (thanks to everyone's suggestions
in the earlier thread). I've also done some benchmarking:
https://build2.org/article/preprocess-compile-performance.xhtml
TL;DR for GCC:
Surprising
On 05/16/2017 09:14 PM, David Malcolm wrote:
> On Mon, 2017-05-15 at 15:36 +0200, Martin Liška wrote:
>> Hi.
>>
>> I sent this email to David some time ago, but it should be probably
>> answered
>> on gcc mailing list.
>
>> I have idea one to improve gcov tool and I'm interested in more
>> precise
Hi,
In that function, we have below comments:
/* Basically, for each pair of dependent data refs store_ptr_0
and load_ptr_0, we create an expression:
((store_ptr_0 + store_segment_length_0) <= load_ptr_0)
|| (load_ptr_0 + load_segment_length_0) <= store_ptr_0))
for aliasing
13 matches
Mail list logo
