From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3560 invoked by alias); 5 Apr 2004 20:47:51 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 3516 invoked from network); 5 Apr 2004 20:47:44 -0000 Received: from unknown (HELO mail.codesourcery.com) (65.74.133.6) by sources.redhat.com with SMTP; 5 Apr 2004 20:47:44 -0000 Received: (qmail 23169 invoked from network); 5 Apr 2004 20:47:43 -0000 Received: from taltos.codesourcery.com (zack@66.92.218.83) by mail.codesourcery.com with DES-CBC3-SHA encrypted SMTP; 5 Apr 2004 20:47:43 -0000 Received: by taltos.codesourcery.com (sSMTP sendmail emulation); Mon, 5 Apr 2004 13:47:37 -0700 To: mec.gnu@mindspring.com (Michael Elizabeth Chastain) Cc: drow@false.org, ezannoni@redhat.com, gdb@sources.redhat.com, jimb@redhat.com Subject: Re: gcc HEAD, stabs+, TYPE_CODE_INT problem References: <20040405202649.104DB4B104@berman.michael-chastain.com> From: Zack Weinberg Date: Mon, 05 Apr 2004 20:47:00 -0000 In-Reply-To: <20040405202649.104DB4B104@berman.michael-chastain.com> (Michael Elizabeth Chastain's message of "Mon, 5 Apr 2004 16:26:49 -0400 (EDT)") Message-ID: <87lllai23a.fsf@egil.codesourcery.com> User-Agent: Gnus/5.110002 (No Gnus v0.2) Emacs/21.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2004-04/txt/msg00031.txt.bz2 mec.gnu@mindspring.com (Michael Elizabeth Chastain) writes: [...] > gcc 3.3.3 (and gcc HEAD 20040323) emitted about 20 stab lines for the > list from first_builtin_decl to last_builtin_decl. This provides gdb > with names for "char", "int", "float", et cetera. gcc HEAD 20040330 no > longer uses provides this list so there are no more stab lines for the > builtin types. Can we change gcc to bring these builtins back? Not emitting them was unintentional, and I imagine getting them back would be straightforward. However, I don't know a lot about dbxout.c and right now I have things to do for the 3.4.0 release (which doesn't include these patches) that take priority - so I'm not likely to try to fix this this week. Would you please file a bug report against GCC, and assign it to me? And any further investigation you could do would be greatly appreciated. zw