From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30443 invoked by alias); 15 Aug 2013 04:01:49 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 30428 invoked by uid 89); 15 Aug 2013 04:01:48 -0000 X-Spam-SWARE-Status: No, score=2.8 required=5.0 tests=AWL,BAYES_50,URI_HEX autolearn=no version=3.3.2 Received: from sam.nabble.com (HELO sam.nabble.com) (216.139.236.26) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Thu, 15 Aug 2013 04:01:47 +0000 Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1V9okr-00005q-T4 for gcc@gcc.gnu.org; Wed, 14 Aug 2013 21:01:45 -0700 Date: Thu, 15 Aug 2013 04:51:00 -0000 From: sculptor To: gcc@gcc.gnu.org Message-ID: <1376539305895-960698.post@n5.nabble.com> Subject: What does the RTX_FLAG volitil mean? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-SW-Source: 2013-08/txt/msg00171.txt.bz2 In poking about the guts of gcc I noticed that the RTX_FLAG volitil seems to be set for some strange reasons... For instance. it's set for registers that receive the value of a parameter register in addition to being set for registers that were declared volatile in the C code. Note, this is not an academic because I really need to figure out which registers were declared as volatile... -- View this message in context: http://gcc.1065356.n5.nabble.com/What-does-the-RTX-FLAG-volitil-mean-tp960698.html Sent from the gcc - Dev mailing list archive at Nabble.com.