From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16766 invoked by alias); 20 Jul 2015 10:36:01 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 16730 invoked by uid 48); 20 Jul 2015 10:35:57 -0000 From: "noloader at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/66943] GCC warns of Unknown Pragma for OpenMP, even though it support it. Date: Mon, 20 Jul 2015 10:36:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 4.8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: noloader at gmail dot com 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-SW-Source: 2015-07/txt/msg01713.txt.bz2 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D66943 --- Comment #6 from Jeffrey Walton --- (In reply to Manuel L=C3=B3pez-Ib=C3=A1=C3=B1ez from comment #5) > ... > For what is worth, I understand the point by Andrew that without -fopenmp, > the #pragmas are effectively ignored, thus the warning seems useful. Perh= aps > it would be more useful a specific -Wopenmp-pragmas that says: >=20 Maybe it could be in effect with `-Wextra`? Enabling Unknown Pragma warnings for #pragma omp under -Wall when the compi= ler supports it, coupled with the inability to manage warnings with 'pragma GCC diagnostic` (Bug #53431), means we just turned OFF -Wall. We are moving in = the wrong direction :( >>From gcc-bugs-return-492824-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 20 10:43:00 2015 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 21106 invoked by alias); 20 Jul 2015 10:43:00 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 21061 invoked by uid 48); 20 Jul 2015 10:42:56 -0000 From: "jiwang at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/63304] Aarch64 pc-relative load offset out of range Date: Mon, 20 Jul 2015 10:43:00 -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: 5.0 X-Bugzilla-Keywords: assemble-failure X-Bugzilla-Severity: normal X-Bugzilla-Who: jiwang at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P5 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2015-07/txt/msg01714.txt.bz2 Content-length: 821 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63304 Jiong Wang changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jiwang at gcc dot gnu.org --- Comment #16 from Jiong Wang --- Have done a quick look at this, basic ideas to fix this: * generate a special pattern which initialize literal pool start address. * implement TARGET_MACHINE_DEPENDENT_REORG to calculate whehter the pc-relative literal load is within range. * output final insruction sequences which initializing literal pool start address based on the result from reorg pass analysis. Use movk/z, adrp + add, single adr for different distance.