From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8942 invoked by alias); 29 Nov 2004 14:13:50 -0000 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 Received: (qmail 8887 invoked by uid 48); 29 Nov 2004 14:13:44 -0000 Date: Mon, 29 Nov 2004 14:13:00 -0000 Message-ID: <20041129141344.8884.qmail@sourceware.org> From: "pinskia at gcc dot gnu dot org" To: gcc-bugs@gcc.gnu.org In-Reply-To: <20041119132256.18566.Thomas.Koenig@online.de> References: <20041119132256.18566.Thomas.Koenig@online.de> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug target/18566] Can vary constants (undefined fortran) X-Bugzilla-Reason: CC X-SW-Source: 2004-11/txt/msg03605.txt.bz2 List-Id: ------- Additional Comments From pinskia at gcc dot gnu dot org 2004-11-29 14:13 ------- This is a target problem, most likely what is happening is that the memory where the variable is being stored is not being marked as read only for the processor. So is this is either an OS problem or just a defientcy in the IA64. -- What |Removed |Added ---------------------------------------------------------------------------- Component|fortran |target Priority|P1 |P3 Summary|Can vary constants |Can vary constants | |(undefined fortran) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18566