Hi -- I'm not a member of the list, so please copy me on replies. Thanks!
I'll just show you the issue:
Horacemann-3:~ horacemann-old$ xcode-select --install
xcode-select: Error: unknown command option '--install'.
xcode-select: Report or change the path to the active
Xcode instal
On 09/11/14 23:37, Prahas David Nafissian wrote:
> I'll just show you the issue:
>
> Horacemann-3:~ horacemann-old$ xcode-select --install
> xcode-select: Error: unknown command option '--install'.
You are probably using OS X 10.8/Mountain Lion. I've never used that OS
X release, and apparently X
How oder where is the addres size for the current compiler target defined?
mfg Steve
___
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
Thank you. My remaining hair follicles (and those
of the future Mtn Lion users attempting to install)
will be eternally grateful. ;-)
On Mon, Nov 10, 2014 at 2:09 AM, Jonas Maebe wrote:
> On 09/11/14 23:37, Prahas David Nafissian wrote:
>> I'll just show you the issue:
>>
>> Horacemann-3:~ ho
Steve Hildebrandt wrote on ma, 10 nov 2014:
How oder where is the addres size for the current compiler target defined?
See the last three entries in table G.2. at
http://www.freepascal.org/docs-html/prog/progap7.html
Alternatively, you can use
{$if sizeof(pointer)=8}
<64 bit pointe
On Mon, 10 Nov 2014, Jonas Maebe wrote:
Steve Hildebrandt wrote on ma, 10 nov 2014:
How oder where is the addres size for the current compiler target defined?
See the last three entries in table G.2. at
http://www.freepascal.org/docs-html/prog/progap7.html
Alternatively, you can use
{$
Am 10.11.2014 um 15:55 schrieb Jonas Maebe:
>
> Steve Hildebrandt wrote on ma, 10 nov 2014:
>
>> How oder where is the addres size for the current compiler target
>> defined?
>
> See the last three entries in table G.2. at
> http://www.freepascal.org/docs-html/prog/progap7.html
>
> Alternatively, y
I think I discovered another issue. Not sure if you are already aware of it.
Don't remember it being reported before.
Seems like using heaptrc feature (memory leak reporting) with refc-compiler
leads to program crashing on exit. In particular, it appears that heaptrc
starts reporting memory le
eh sorry; false alarm. You know how it is, when encountering a bug, you first
think that it's someone else's fault)) or maybe it's just me who tends to think
in such way((.
It works))
10.11.2014, 18:47, "hinsta...@yandex.ru" :
> I think I discovered another issue. Not sure if you are already aw
Steve Hildebrandt wrote on ma, 10 nov 2014:
Sry I should have mentioned I'm currently working on the compiler and
I'm not to sure if I can use OS_ADDR for RTTI generation.
If you want a tcgsize, use def_cgsize(voidcodepointertype) for
references to code and def_cgsize(voidpointertype) for r
Am 10.11.2014 um 16:58 schrieb Jonas Maebe:
>
> Steve Hildebrandt wrote on ma, 10 nov 2014:
>
>> Sry I should have mentioned I'm currently working on the compiler and
>> I'm not to sure if I can use OS_ADDR for RTTI generation.
>
> If you want a tcgsize, use def_cgsize(voidcodepointertype) for
> re
Hi,
We were profiling our code, and one RTL function regularly popped up in
close to the top in the profiling list.
It's remove_freed_fixed_chunks(). Can someone explain to me under what
condition this code is triggered very often and/or could take long to
execute (there's a loop in there)?
Mayb
12 matches
Mail list logo
