Hi,
On Mon, 11 Jan 2021, Sven Barth via fpc-devel wrote:
> So the idea is to add support for ROL/ROR with Carry support as the
> current Rol*/Ror* functions don't support that. Florian then said that
> he's open to suggestions under some restrictions. Considering that the
> current Rol*/Ror* intr
Hi
On Mon, 19 Apr 2021, Curtis Hamilton via fpc-devel wrote:
>> Thanks for reaching back. I’d the feeling that there wasn’t much
>> interest when I didn’t get a lot of feedback from the FreeBSD/PowerPC
>> community.
>>
>> I’ve looked at the changes to support aarch64. I’ve already gotten
>
Hi
On Sun, 8 Aug 2021, Florian Klämpfl via fpc-devel wrote:
> > One of the guys responsible for glibc in Fedora gave this explanation:
> >
> >> It's related to startup code hardening in glibc. In general, it's
> >> not forward-compatible to call internal glibc functions this way.
> >> __libc_csu
Hi,
On Sun, 12 Dec 2021, Yuriy Sydorov via fpc-devel wrote:
> > set CPUOPTS=-O2 -Opcoreavx -Cpcoreavx
> > set CPUOPTS64=-Cfavx
> >
> > I didn't enter those in Lazarus I think, so that should be pretty much
> default.
>
> Should be fixed now. The AVs have occurred only when targeting the AVX FPU.
Hi,
On Mon, 13 Dec 2021, Yuriy Sydorov via fpc-devel wrote:
> > I've no doubt the problem is in the m68k target, and the IE only exposed
> > it, but regardless, register allocation is not one of my strenght, so
> > ideas welcomed.
>
> The new internal error catches incorrect usage of get_alias().
Hi,
On Tue, 25 Jan 2022, Thorsten Otto via fpc-devel wrote:
> Yes, a.out support (which is used on Atari) has been dropped in 2.31.
> But i've added it back in, and cross-binutils of 2.34 can be found at
> http://tho-otto.de/crossmint.php#binutils
Won't really help. As you found out already, sec
Hi,
On Tue, 25 Jan 2022, Thorsten Otto via fpc-devel wrote:
> Yes, but i never used that "brown" tool. For one, i don't like its
> confusing naming convention (depending on gcc version, it is "brown",
> "extrabrown", "superbrown" etc). But more importantly, it needs an extra
> tool to be run afte
Hi,
On Tue, 25 Jan 2022, Thorsten Otto via fpc-devel wrote:
> > And of course i have to find out what causes vlink to put that strange
> > program flags in the header.
>
> I think i found the reason for that. The offending lines in vlink/main.c are:
> (...)
> (at this point the option argument ha
Hi,
On Fri, 28 Jan 2022, Thorsten Otto via fpc-devel wrote:
> On Freitag, 28. Januar 2022 13:55:11 CET Thorsten Otto via fpc-devel wrote:
>
> > i still want to try to figure out what's wrong when using gas/ld)
> I get the the feeling that there must be something else going wrong:
>
> - when i ru
Hi,
On Sat, 29 Jan 2022, Thorsten Otto via fpc-devel wrote:
> On Freitag, 28. Januar 2022 20:21:03 CET Karoly Balogh wrote:
>
>> a fixed GAS/LD support would be nice, of course.
>
> Yes, but currently i'm a bit lost here. Since that combination currently
> does not support "smart linking", i gues
Hi,
On Sat, 29 Jan 2022, Karoly Balogh via fpc-devel wrote:
> > There are other parts that should be improved, and seem more important
> > to me (like ARGV support, completing the GEMDOS/BIOS/XBIOS interface
> > etc)
>
> Totally agree here.
Just one more note here, for t
Hi,
On Sat, 29 Jan 2022, Thorsten Otto via fpc-devel wrote:
>> Again, this isn't a generic problem, but Atari specific.
>
> Yes, but theoretically, win32 should have the same problem. As far as
> i've seen, ReadFile() is used there. but fpc_readln_end() tries to read
> until it encounters a LF, a
Hi,
On Tue, 1 Feb 2022, Thorsten Otto via fpc-devel wrote:
> On Dienstag, 1. Februar 2022 09:11:21 CET Pierre Muller via fpc-devel wrote:
>
> > thus you should use
> > -Aas-out
> > compiler option.
>
> Ah thx. Would make more sense to just use "as" like for other targets,
> but i see that this ta
Hi,
On Sun, 6 Feb 2022, Thorsten Otto via fpc-devel wrote:
> > - Running the same binaries in SingleTOS, they both give me "Internal
> > error 2004121202'. Then they both crash with a bus-error, too.
>
> That internal error is currently striking back. This happens both with
> my own compiled bina
Hi,
On Mon, 7 Feb 2022, Thorsten Otto via fpc-devel wrote:
> > On Montag, 7. Februar 2022 10:31:01 CET Thorsten Otto via fpc-devel wrote:
>
> > Nice, that's it. Compiling everything for 68020, and it works.
>
> Hm, or maybe not. A few hours later, installing a freshly compiled
> version, i get th
Hi,
On Mon, 7 Feb 2022, Thorsten Otto via fpc-devel wrote:
> > It's just that you need to provide it with the correctly compiled units
>
> Yes, i see. But that requires some manual fiddling with the library
> directories, and you need both 68000 and 68020 versions somehow.
>
> How do the Amiga fo
Hi,
On Mon, 7 Feb 2022, Karoly Balogh via fpc-devel wrote:
> Not under mind, but going with this would probably mean
> giving up TOS support.
*Not under MINT, I mean, sorry for the typo.
Charlie
___
fpc-devel maillist - fpc
Hi,
On Mon, 7 Feb 2022, Thorsten Otto via fpc-devel wrote:
> > but going with this would probably mean giving up TOS support.
>
> Yes, that 8.3 restriction might be the worst that was ever made. But
> even unices of that time allowed only 14 character long filenames.
It is also the main reason w
Hi,
On Thu, 10 Feb 2022, Sven Barth via fpc-devel wrote:
> Thorsten Otto via fpc-devel schrieb am
> Do., 10. Feb. 2022, 15:47:
>
>>> Cause in the variant you mentioned where would the allocated memory be
>>> stored?
>> I'm not that familiar with ObjectGEM yet, but i think the
>> allocated pointe
Hi,
On Sat, 12 Feb 2022, Thorsten Otto via fpc-devel wrote:
> I'm currently trying to set this up and have a problem with the
> cross-compiler. Although that was configured for atari and 68000, it
> still has LINUX and CPU68020 defined while processing the config file.
That probably can't be hel
Hi,
On Sat, 12 Feb 2022, Florian Klämpfl via fpc-devel wrote:
> >> My config file has -Tatari set, so the LINUX define is no issue. But if
> >> i invoke the compiler without excplicit -Cp, it will generate code
> >> for 68000, but take the libraries from the 68020 directory. It works as
> >> inte
Hi,
This e-mail was sent as a test of our ML infrastructure after a server
upgrade. Please ignore.
Charlie
___
fpc-devel maillist - fpc-devel@lists.freepascal.org
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
Hi,
On Tue, 12 Apr 2022, J. Gareth Moreton via fpc-devel wrote:
> To complement aligned records, I'm trying out an implementation of
> aligned records. Like how you might declare an aligned record as follows:
>
> type AlignedVector = packed record
> X, Y: Double;
> end align 16;
Is this "a
Hi,
On Fri, 19 Aug 2022, Michael Van Canneyt via fpc-devel wrote:
> > With actual FPC main (61debb15) got the below error. No error with an
> > earlier FPC main (8028a769). Any idea?
>
> It's a pretty basic unit, I can't imagine that it would not have been
> compiled.
I think such errors are als
Hi,
On Thu, 10 Nov 2022, Sven Barth via fpc-devel wrote:
> You still need to feed the model with the necessary rules and with
> necessary training data of both correct and incorrect approaches.
>
> But even then *I* wouldn't want to have any of that black box mambo
> jumbo in FPC, cause when a bu
Hello,
This is a test e-mail following some listsserver maintenance, please
ignore.
Charlie
___
fpc-devel maillist - fpc-devel@lists.freepascal.org
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
Hi,
On Fri, 4 Oct 2024, Adriaan van Os via fpc-devel wrote:
> My question now is if there is a reason why FPC doesn't call backtrace (see
> man backtrace) on Linux and Unix (including MacOS) platforms ?
It seems this is a relatively recent addition to libc, which means, after
2000. :)
I suppose
Hi,
On Mon, 28 Oct 2024, Mattias Gaertner via fpc-devel wrote:
> On mac the linker gives
>
> Error: -macosx_version_min has been renamed to -macos_version_min
>
> With fpc 3.2.2 and 3.3.1.
>
> Is there some option I'm missing?
This has been a warning before. Maybe Apple changed it to an error
re
Hi,
On Sat, 28 Sep 2024, Martin Frb via fpc-devel wrote:
> About the big endian issue: That means it is not memory compatible with a
> native "extended" because it has a gap.
Fromt the top of my head, I only know one example of a big endian system
which has an 80 bit extended type in hardware, a
29 matches
Mail list logo
