From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 329BF3857C42; Fri, 24 Jul 2020 07:32:43 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 329BF3857C42 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1595575963; bh=9CzhTHfB7gROMtr9CtJuC/s3MD9oBWqgPdU6baSE8Kg=; h=From:To:Subject:Date:In-Reply-To:References:From; b=EIDV48lEYMEehDWl+eP2BzZJwC11GpaWo21K859aset4RD50tYypXd5wknBVImoCf WvLHnidOxLPt0HqHpeCLn8+A2M6fTTssGkV40MqxEajfzsude120mQqBK/Q/VEFNI6 K9Fhll0ZL9l70dmTzu+HBcrKIjDoxLZNPi4d80E4= From: "jakub at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/96306] gcn libgomp build broken after "libomp: Add omp_depend_kind to omp_lib.{f90,h}" Date: Fri, 24 Jul 2020 07:32:43 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 11.0 X-Bugzilla-Keywords: openacc, openmp X-Bugzilla-Severity: normal X-Bugzilla-Who: jakub at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: gcc-bugs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-bugs mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jul 2020 07:32:43 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D96306 --- Comment #1 from Jakub Jelinek --- Unlike non-offloading targets where there is always an option to just use smaller omp_depend_kind and instead treat it as pointer to malloced struct = and free at the end, like done on some targets for locks, for offloading targets I'm afraid this is problematic, because the sources will really use 16-byte omp_depend_kind anyway on most of the lp64 hosts. So, what are the obstackles to support TImode on gcn? After all, users can just use __int128_t etc. in their programs too.=