From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27968 invoked by alias); 9 Jul 2015 20:04:06 -0000 Mailing-List: contact jit-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Subscribe: Sender: jit-owner@gcc.gnu.org Received: (qmail 27954 invoked by uid 89); 9 Jul 2015 20:04:05 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Checked: by ClamAV 0.98.7 on sourceware.org X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.5 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_LOW autolearn=no version=3.3.2 X-Spam-Status: No, score=-1.5 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_LOW autolearn=no version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on sourceware.org X-Spam-Level: X-HELO: mail-yk0-f180.google.com X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=/l2ns5dJGwxm5mfgptQKbgYPefd6vY8d437QIU8wsnE=; b=LoaJDJBGv9sCQQr2hYHSVlvYcYp9CWcpO+Dsl3r+MwriYoY68F/rc6trVZ5hPrrCAN WzNWK0XmDbO0d8wDEq5J+hVYhdHVt3dWM/LOgrlZL+NlRoutHxH/RoeI2GprUkBQq08k wVHmBIsLJC9XlFoNaPn0L3SqczMETRKY1Rm0YjUT8mmQrCi6WBRr8YAipS/bShr8grYB Bp48M7DeaagTys+7RS/yR5Apd3NoyTpRFfGPerC8qGl7yKk2yG/7Da7KmpCG53Hnyqnc YJBQdzJ68R5F5c+ywYLT9HxkXVtfzQ5DUn9kl23TgACuGPdn7V1JykxkfEy1kj6r/LzS Jgnw== X-Gm-Message-State: ALoCoQnEKrvqctsw6co0Fj0A9rrH9OexB3UQgoevFjnDK6ovYKaY3Xh7z2liRi8dPR5x7kJ6/Ped MIME-Version: 1.0 X-Received: by 10.13.212.199 with SMTP id w190mr19397816ywd.57.1436472242485; Thu, 09 Jul 2015 13:04:02 -0700 (PDT) In-Reply-To: <1436469387.24803.150.camel@surprise> References: <1436365266.24803.65.camel@surprise> <1436367926.24803.71.camel@surprise> <1436369443.24803.75.camel@surprise> <1436377619.24803.97.camel@surprise> <1436403792.24803.112.camel@surprise> <1436469387.24803.150.camel@surprise> Date: Thu, 01 Jan 2015 00:00:00 -0000 Message-ID: Subject: Re: Filed PR jit/66812 for the code generation issue From: Dibyendu Majumdar To: David Malcolm Cc: jit@gcc.gnu.org Content-Type: text/plain; charset=UTF-8 X-SW-Source: 2015-q3/txt/msg00056.txt.bz2 On 9 July 2015 at 20:16, David Malcolm wrote: > I've managed to create a minimal reproducer for this; see: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66812 > where libgccjit miscompiles it, but the C frontend (cc1) handles the > equivalent C code just fine (even at -O3, without needing > -fno-strict-aliasing). > > So the next step seems to be to step through the fre1 pass in both > libgccjit and in cc1, and to see what's different. > > Yay, progress! > Indeed! Sorry for all the trouble - obviously this one is not easy to diagnose. Regards