From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25265 invoked by alias); 14 Dec 2007 22:30:45 -0000 Received: (qmail 25192 invoked by uid 22791); 14 Dec 2007 22:30:44 -0000 X-Spam-Check-By: sourceware.org Received: from smtp-out.google.com (HELO smtp-out.google.com) (216.239.45.13) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 14 Dec 2007 22:30:40 +0000 Received: from zps37.corp.google.com (zps37.corp.google.com [172.25.146.37]) by smtp-out.google.com with ESMTP id lBEMUbhe016810 for ; Fri, 14 Dec 2007 14:30:37 -0800 Received: from py-out-1112.google.com (pybu52.prod.google.com [10.34.97.52]) by zps37.corp.google.com with ESMTP id lBEMSaU6027759 for ; Fri, 14 Dec 2007 14:30:36 -0800 Received: by py-out-1112.google.com with SMTP id u52so1680145pyb.10 for ; Fri, 14 Dec 2007 14:30:36 -0800 (PST) Received: by 10.64.10.2 with SMTP id 2mr8359816qbj.2.1197671436194; Fri, 14 Dec 2007 14:30:36 -0800 (PST) Received: by 10.65.148.3 with HTTP; Fri, 14 Dec 2007 14:30:36 -0800 (PST) Message-ID: <498552560712141430q75098aaembcda8db5c6edd8fb@mail.gmail.com> Date: Fri, 14 Dec 2007 22:30:00 -0000 From: "=?BIG5?B?RG91ZyBLd2FuICjD9q62vHcp?=" To: gcc@gcc.gnu.org, gdb@sourceware.org Subject: Adding new dwarf encoding formats for complex integers MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2007-12/txt/msg00093.txt.bz2 Hi, I am working on the gcc LTO project and I found that gcc does not generate sufficient debugging information for complex integer types. Currently gcc uses encoding DW_ATE_lo_user ( 0x80) for complex integer types but that 1) clashes with an HP extension and 2) does not distinguish between complex signed integer and complex unsigned integer types. I'm thinking about adding DW_ATE_GNU_complex_signed (0x87) and DW_ATE_GNU_complex_unsigned (0x88) encoding formats. Is there anything I need to do in addition to changing gcc? Are there people I should talk to? And what documentation should be updated? Currently gdb (I checked 6.7) does not support complex integer properly. So it needs to be changed anyway. -Doug