From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.3 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,NICE_REPLY_A,SPF_HELO_NONE, SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id A365FC43462 for ; Wed, 5 May 2021 17:27:14 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 74762610E7 for ; Wed, 5 May 2021 17:27:14 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S237532AbhEER2K (ORCPT ); Wed, 5 May 2021 13:28:10 -0400 Received: from mga12.intel.com ([192.55.52.136]:25660 "EHLO mga12.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S240814AbhEERVz (ORCPT ); Wed, 5 May 2021 13:21:55 -0400 IronPort-SDR: Gy5WfCCn8aFWi/mK5icurepG65pTP4/nbE5fdG3WmiDuQiKHKxHoJHeYx1mX6tyownRGoe2QTR DFu2uKJRLyPg== X-IronPort-AV: E=McAfee;i="6200,9189,9975"; a="177816675" X-IronPort-AV: E=Sophos;i="5.82,276,1613462400"; d="scan'208";a="177816675" Received: from orsmga008.jf.intel.com ([10.7.209.65]) by fmsmga106.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 05 May 2021 10:20:55 -0700 IronPort-SDR: o0yYawx1/oCR50PF9y3RQo/kL4Ul4IoEzby+KDd4eOIHGD4boO5vcuxfAg3lZsk6M6TWjvEHWX nxfZZdfaeNjA== X-IronPort-AV: E=Sophos;i="5.82,276,1613462400"; d="scan'208";a="433926393" Received: from akleen-mobl1.amr.corp.intel.com (HELO [10.209.54.13]) ([10.209.54.13]) by orsmga008-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 05 May 2021 10:20:54 -0700 Subject: Re: [PATCH] sched: Work around undefined behavior in sched class checking To: Nick Desaulniers Cc: Florian Weimer , Peter Zijlstra , LKML , Andi Kleen , linux-toolchains@vger.kernel.org References: <20210505033945.1282851-1-ak@linux.intel.com> <875yzxh8j8.fsf@oldenburg.str.redhat.com> <20210505143916.GS4032392@tassilo.jf.intel.com> From: Andi Kleen Message-ID: <37defc3e-4050-d8c5-c056-fdf64f516098@linux.intel.com> Date: Wed, 5 May 2021 10:20:54 -0700 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.10.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US Precedence: bulk List-ID: X-Mailing-List: linux-toolchains@vger.kernel.org >> But not sure why you want a test case? > In general, > when making a feature request to a compiler vendor, having a > digestible snippet of code that demonstrates the problem goes a long > way, much further than "clone this branch of my fork of this project > and do a build and something goes wrong somewhere." We're too busy to > do that, please take the time to isolate it before making such > requests. Ah you misunderstood. I'm not making any feature requests. -Andi