Paul Ishenin het geskryf:
12.03.2010 23:51, Paul Ishenin wrote:
If something more is required please let me know and I will search.
Also found the next document with more info:
http://www.agner.org/optimize/calling_conventions.pdf
And here is more information.
On 15 Mar 2010, at 04:01, Paul Ishenin wrote:
12.03.2010 21:49, Jonas Maebe wrote:
The default calling convention could be used. This would only work
for
routines with simple return types though (types that are not
returned
via a hidden first parameter).
I don't think any/default
On 15 Mar 2010, at 07:49, Graeme Geldenhuys wrote:
And here is more information.
http://docwiki.embarcadero.com/RADStudio/en/Program_Control
Thank you, that is the information that was needed:
For a string, dynamic array, method pointer, or variant result, the
effects are the same as if
15.03.2010 17:01, Jonas Maebe wrote:
the only problem in that respect is that without the hacky
patch mentioned earlier, GDB's Pascal parser does not support expressing
method calls.
The remaining question for me is whether you will implement that hacky
patch :) ?
Best regards,
Paul
On 15 Mar 2010, at 11:12, Paul Ishenin wrote:
15.03.2010 17:01, Jonas Maebe wrote:
the only problem in that respect is that without the hacky
patch mentioned earlier, GDB's Pascal parser does not support
expressing
method calls.
The remaining question for me is whether you will
On Mon, Mar 15, 2010 at 7:31 AM, Jonas Maebe jonas.ma...@elis.ugent.be wrote:
On 15 Mar 2010, at 11:12, Paul Ishenin wrote:
15.03.2010 17:01, Jonas Maebe wrote:
the only problem in that respect is that without the hacky
patch mentioned earlier, GDB's Pascal parser does not support
On 15 Mar 2010, at 14:13, Flávio Etrusco wrote:
On Mon, Mar 15, 2010 at 7:31 AM, Jonas Maebe jonas.ma...@elis.ugent.be
wrote:
On 15 Mar 2010, at 11:12, Paul Ishenin wrote:
15.03.2010 17:01, Jonas Maebe wrote:
the only problem in that respect is that without the hacky
patch mentioned
12.03.2010 21:49, Jonas Maebe wrote:
The default calling convention could be used. This would only work for
routines with simple return types though (types that are not returned
via a hidden first parameter).
I don't think any/default calling convention have result return in EAX
as fpc do.
On Fri, 12 Mar 2010, Paul Ishenin wrote:
Hello, FPC developers' list.
I know at the moment we have the next problems which cause subj don't work:
1. gdb does not supports borland fastcall calling convention (delphi calls it
register though)
2. fpc does not write debug info for properties
12.03.2010 15:11, Michael Van Canneyt wrote:
You mean in the gdb info only, I hope ?
dwarf debug info.
Best regards,
Paul Ishenin.
___
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-devel
On 12 Mar 2010, at 02:44, Paul Ishenin wrote:
I know at the moment we have the next problems which cause subj
don't work:
1. gdb does not supports borland fastcall calling convention (delphi
calls it register though)
2. fpc does not write debug info for properties with getters because
On 12 Mar 2010, at 02:44, Paul Ishenin wrote:
1. gdb does not supports borland fastcall calling convention (delphi
calls it register though)
PS: one reason that this is not advancing is because FPC does not
support it correctly either, and I don't want to add support for a
broken
: [fpc-devel] properties with getter
evaluation in gdb
Reply-To: FPC-Pascal users discussions fpc-pas...@lists.freepascal.org
On 12 Mar 2010, at 16:23, Flávio Etrusco wrote:
I only have a hack for b) currently, because it makes accessing
fields
case-sensitive in GDB's Pascal mode (which means
12.03.2010 21:55, Jonas Maebe wrote:
PS: one reason that this is not advancing is because FPC does not
support it correctly either, and I don't want to add support for a
broken implementation to GDB since then it has to be changed again
later anyway. I also don't know of any description of
12.03.2010 23:51, Paul Ishenin wrote:
If something more is required please let me know and I will search.
Also found the next document with more info:
http://www.agner.org/optimize/calling_conventions.pdf
Best regards,
Paul Ishenin.
___
fpc-devel
On 12 Mar 2010, at 17:59, Paul Ishenin wrote:
12.03.2010 23:51, Paul Ishenin wrote:
If something more is required please let me know and I will search.
Also found the next document with more info:
http://www.agner.org/optimize/calling_conventions.pdf
It describes what we implement
On Fri, Mar 12, 2010 at 2:11 PM, Jonas Maebe jonas.ma...@elis.ugent.be wrote:
On 12 Mar 2010, at 17:59, Paul Ishenin wrote:
12.03.2010 23:51, Paul Ishenin wrote:
If something more is required please let me know and I will search.
Also found the next document with more info:
On 12 Mar 2010, at 18:25, Flávio Etrusco wrote:
Can't we ask someone from Borland/Embarcadero?
That's indeed a good idea, I don't think anyone has already done that.
Are they that cheap to
hold back such kind of information?
I'm not aware of them being cheap in this or in other ways.
On Fri, Mar 12, 2010 at 9:43 PM, Jonas Maebe jonas.ma...@elis.ugent.be wrote:
Are they that cheap to
hold back such kind of information?
I'm not aware of them being cheap in this or in other ways.
Quite official, i guess:
http://docwiki.embarcadero.com/RADStudio/en/Fastcall,_fastcall
On 12 Mar 2010, at 19:50, dmitry boyarintsev wrote:
Quite official, i guess:
http://docwiki.embarcadero.com/RADStudio/en/Fastcall,_fastcall
Yes, but it is not the full documentation.
Jonas
___
fpc-devel maillist - fpc-devel@lists.freepascal.org
On Fri, Mar 12, 2010 at 10:04 PM, Jonas Maebe jonas.ma...@elis.ugent.be wrote:
Yes, but it is not the full documentation.
yep. I guess is the source for the the information give at wikipedia :)
Anyway, following Flávio's suggestion:
Hello, FPC developers' list.
I know at the moment we have the next problems which cause subj don't work:
1. gdb does not supports borland fastcall calling convention (delphi
calls it register though)
2. fpc does not write debug info for properties with getters because of
point 1.
Let's see
22 matches
Mail list logo
