Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: jonas.maebe@elis.ugent.be
Cc: brobecker@adacore.com, tromey@redhat.com,
	mark.kettenis@xs4all.nl,         gdb-patches@sourceware.org
Subject: Re: [patch] Set calling convention of methods
Date: Fri, 02 Oct 2009 09:21:00 -0000	[thread overview]
Message-ID: <200910020919.n929JEKt029120@brahms.sibelius.xs4all.nl> (raw)
In-Reply-To: <C3FC6AD4-40BC-4CC2-8E6F-AFAA072EDC70@elis.ugent.be> (message 	from Jonas Maebe on Thu, 1 Oct 2009 11:17:54 +0200)

> From: Jonas Maebe <jonas.maebe@elis.ugent.be>
> Date: Thu, 1 Oct 2009 11:17:54 +0200
> 
> > Overall, this looks OK to me, but Mark seemed interested in reviewing
> > this patch, so please wait for his comments as well.
> 
> Ok. Note that my mail client is known to wrap text at 80 columns (and  
> adds a space at the end of each wrapped line for detecting this  
> operation). This behaviour cannot be disabled afaik, and yes, one  
> could certainly consider this to be a bug. At the same time, it  
> however also adds '"Format="flowed"; DelSp="yes"' to the Content-Type  
> header, so mail clients on the other side can reconstruct the original  
> text (if those clients support these modifiers, which I hope is the  
> case).

It's sad that modern graphical e-mail clients get in the way here and
generate all this complicated crap.

Some people using similarly broken mail clients circumvent the problem
by including a diff both inline and as an attachment.  While not
ideal, that's an acceptable solution to me.

> 2009-10-01  Jonas Maebe  <jonas.maebe <at> elis.ugent.be>
> 
> 	Add support for the "Borland fastcall" calling convention.
> 
> 	* dwarf2.h: Add DW_CC_GNU_borland_fastcall_i386 constant.
> 	* i386-tdep.c: #include dwarf2.h
> 	(i386_borland_fastcall_push_dummy_call): New.
> 	(i386_push_dummy_generic_call): Renamed i386_push_dummy_call.
> 	(i386_push_dummy_call): New dispatch function that calls
> 	i386_generic_push_dummy_call or i386_push_dummy_borland_fast_call
> 	depending on the calling convention.
> 	* gdb.dwarf2/dw2-borland_fastcall.exp: New.
> 	* gdb.dwarf2/dw2-borland_fastcall.S: New.

The i386-tdep.c bits are fine with me.  I haven't been following the
dwarf2.h discussion too closely; whatever consensus that's reached
there is fine with me.


  parent reply	other threads:[~2009-10-02  9:21 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-06 19:51 Jonas Maebe
2009-04-10 17:34 ` Tom Tromey
2009-04-20  8:40   ` Jonas Maebe
2009-04-20 18:27     ` Tom Tromey
2009-04-22 17:45       ` Jonas Maebe
2009-04-22 19:22         ` Tom Tromey
2009-04-22 22:16         ` Mark Kettenis
2009-06-04  8:23           ` Jonas Maebe
2009-06-04 18:19             ` Tom Tromey
2009-06-10 20:44               ` Jonas Maebe
2009-06-18 21:45                 ` Fwd: " Jonas Maebe
2009-09-30  0:02                 ` Joel Brobecker
2009-09-30 11:18                   ` Jonas Maebe
2009-09-30 14:54                     ` Jonas Maebe
2009-09-30 15:22                       ` Mark Kettenis
2009-09-30 16:25                       ` Joel Brobecker
2009-10-01  9:18                         ` Jonas Maebe
2009-10-01 22:04                           ` Joel Brobecker
2009-10-02  9:21                           ` Mark Kettenis [this message]
2009-09-30 16:10                     ` Joel Brobecker
2009-09-30 17:36                       ` Joel Brobecker
2009-09-30 16:47                     ` Tom Tromey
2009-09-30 17:32                       ` Joel Brobecker
2009-09-30 17:35                         ` Tom Tromey
2009-10-01  9:21                           ` Jonas Maebe
2009-11-03  9:43                         ` Jonas Maebe
2009-11-03 14:19                           ` Joel Brobecker
2009-07-06 20:50               ` Jonas Maebe

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=200910020919.n929JEKt029120@brahms.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jonas.maebe@elis.ugent.be \
    --cc=tromey@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