From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30880 invoked by alias); 22 May 2006 09:11:28 -0000 Received: (qmail 27006 invoked by uid 48); 22 May 2006 09:09:35 -0000 Date: Mon, 22 May 2006 09:11:00 -0000 Subject: [Bug fortran/27715] New: Extented ASCII characters lead to wrong "CASE" selection X-Bugzilla-Reason: CC Message-ID: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "P dot Schaffnit at access dot rwth-aachen dot de" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2006-05/txt/msg02130.txt.bz2 List-Id: Hi! I am under the impression that using "extended ASCII" wrecks "CASE constructs"... (see example hereafter). Cheers! Philippe PS: The following code lands on the default: ! PROGRAM Test ! CHARACTER ( LEN = 1 ) :: Letter ! Letter = "c" SELECT CASE ( Letter ) CASE ( "c", "รง" ) WRITE ( 6, "(A)" ) "Expected" CASE DEFAULT WRITE ( 6, "(A)" ) "Surprising" END SELECT ! END PROGRAM Test ! PPPS: I' using: Using built-in specs. Target: i686-pc-linux-gnu Configured with: /USER/philippe/Irix/Gcc_Sources/configure --prefix=/usr1/MICRESS/Philippe/Tools/Gcc --enable-languages=c,fortran --disable-maintainer-mode --disable-shared --with-mpfr=/usr1/MICRESS/Philippe/Tools/Mpfr --with-gmp=/usr1/MICRESS/Philippe/Tools/Gmp Thread model: posix gcc version 4.2.0 20060519 (experimental) -- Summary: Extented ASCII characters lead to wrong "CASE" selection Product: gcc Version: 4.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: P dot Schaffnit at access dot rwth-aachen dot de GCC build triplet: i686-pc-linux-gnu GCC host triplet: i686-pc-linux-gnu GCC target triplet: i686-pc-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27715