public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/6392] Problems with __restrict__ type qualifier (array)
Date: Thu, 09 Oct 2003 08:39:00 -0000	[thread overview]
Message-ID: <20031009083940.6014.qmail@sources.redhat.com> (raw)
In-Reply-To: <20020421061600.6392.schmid@snake.iap.physik.tu-darmstadt.de>

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=6392



------- Additional Comments From cvs-commit at gcc dot gnu dot org  2003-10-09 08:39 -------
Subject: Bug 6392

CVSROOT:	/cvs/gcc
Module name:	gcc
Changes by:	jason@gcc.gnu.org	2003-10-09 08:39:34

Added files:
	gcc/testsuite/g++.dg/ext: restrict1.C 

Log message:
	PR c++/6392
	* cp/tree.c (build_cplus_array_type): Handle all quals the same.
	(cp_build_qualified_type_real): Look through arrays first.
	* c-common.c (c_build_qualified_type): Look through arrays first.
	(c_apply_type_quals_to_decl): Look through arrays.

Patches:
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/g++.dg/ext/restrict1.C.diff?cvsroot=gcc&r1=NONE&r2=1.1


  parent reply	other threads:[~2003-10-09  8:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20020421061600.6392.schmid@snake.iap.physik.tu-darmstadt.de>
2003-06-28  4:37 ` pinskia at physics dot uc dot edu
2003-08-29 21:13 ` jason at gcc dot gnu dot org
2003-10-09  8:39 ` cvs-commit at gcc dot gnu dot org [this message]
2003-10-09  8:39 ` cvs-commit at gcc dot gnu dot org
2003-10-09 14:55 ` pinskia at gcc dot gnu dot org
2003-10-09 15:30 ` jason at gcc dot gnu dot org
2003-12-26  3:28 ` [Bug optimization/6392] " pinskia at gcc dot gnu dot org
2005-09-28  5:17 ` [Bug middle-end/6392] " ian at airs dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20031009083940.6014.qmail@sources.redhat.com \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).