From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15420 invoked by alias); 12 Jul 2002 18:06:01 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 15405 invoked by uid 71); 12 Jul 2002 18:06:01 -0000 Date: Fri, 12 Jul 2002 11:06:00 -0000 Message-ID: <20020712180601.15404.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: Frank van der Linden Subject: Re: target/6912: x86_64 switch code generation problem with -fPIC Reply-To: Frank van der Linden X-SW-Source: 2002-07/txt/msg00385.txt.bz2 List-Id: The following reply was made to PR target/6912; it has been noted by GNATS. From: Frank van der Linden To: gcc-gnats@gcc.gnu.org Cc: Subject: Re: target/6912: x86_64 switch code generation problem with -fPIC Date: Fri, 12 Jul 2002 19:57:41 +0200 As of 20020711, both the trunk and the 3.1 branch seem to generate correct code again. The 3.1 branch uses a correct movslq, and -current, while not doing the sign extension, always seems to put the jumptable in the text segment, right after the table index + jump code. So the offsets are always positive.