Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sources.redhat.com, binutils@sources.redhat.com
Subject: Re: IBM C compiler patch for GDB 6.1
Date: Thu, 03 Jun 2004 03:16:00 -0000	[thread overview]
Message-ID: <20040603031557.GA920@nevyn.them.org> (raw)
In-Reply-To: <20040602224326.GA92326@mail1.thewrittenword.com>

This is a binutils file rather than a GDB one.  I think the patch looks
reasonable...

On Wed, Jun 02, 2004 at 05:43:26PM -0500, Albert Chin wrote:
> The IBM compiler doesn't like bit types to be of type char:
>   ...
>   xlc -DHAVE_CONFIG_H -I. -I. -I. -D_GNU_SOURCE -DAIX_5_CORE -DAIX_CORE_DUMPX_CORE -DAIX_CORE -DAIX_WEAK_SUPPORT -I. -I. -I./../include -I./../intl -I../intl -O2 -qmaxmem=-1 -qarch=com -c bfd.c  -DPIC
>   1506-507 (W) No licenses available. Contact your program supplier to add additional users. Compilation will proceed shortly.
>   "elf-bfd.h", line 281.3: 1506-009 (S) Bit-field cie must be of type signed int, unsigned int or int.
>   "elf-bfd.h", line 282.3: 1506-009 (S) Bit-field removed must be of type signed int, unsigned int or int.
>   "elf-bfd.h", line 283.3: 1506-009 (S) Bit-field make_relative must be of type signed int, unsigned int or int.
>   "elf-bfd.h", line 284.3: 1506-009 (S) Bit-field make_lsda_relative must be of type signed int, unsigned int or int.
>   "elf-bfd.h", line 285.3: 1506-009 (S) Bit-field per_encoding_relative must be of type signed int, unsigned int or int.
> 
> Patch below.
> 
> -- 
> albert chin (china@thewrittenword.com)
> 
> -- snip snip
> 2004-06-02  Albert Chin-A-Young  <china@thewrittenword.com>
> 
> 	* bfd/elf-bfd.h: Convert unsigned char bit types to
> 	unsigned int to satisfy IBM C compiler.
> 
> --- bfd/elf-bfd.h.orig	2004-05-27 00:31:45.546121000 -0500
> +++ bfd/elf-bfd.h	2004-05-27 00:31:54.296250000 -0500
> @@ -278,11 +278,11 @@
>    unsigned char fde_encoding;
>    unsigned char lsda_encoding;
>    unsigned char lsda_offset;
> -  unsigned char cie : 1;
> -  unsigned char removed : 1;
> -  unsigned char make_relative : 1;
> -  unsigned char make_lsda_relative : 1;
> -  unsigned char per_encoding_relative : 1;
> +  unsigned int cie : 1;
> +  unsigned int removed : 1;
> +  unsigned int make_relative : 1;
> +  unsigned int make_lsda_relative : 1;
> +  unsigned int per_encoding_relative : 1;
>  };
>  
>  struct eh_frame_sec_info
> 

-- 
Daniel Jacobowitz


      reply	other threads:[~2004-06-03  3:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-02 22:43 Albert Chin
2004-06-03  3:16 ` Daniel Jacobowitz [this message]

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=20040603031557.GA920@nevyn.them.org \
    --to=drow@false.org \
    --cc=binutils@sources.redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    /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