Re: [fpc-pascal] glGetString crash

2018-02-19 Thread Ryan Joseph
> On Feb 20, 2018, at 4:24 AM, Jonas Maebe wrote: > > My guess is that the Load_GL_VERSION_3_3x() function is broken since it > appears to call glGetString before a context has been created, and that it > just happens to work on some (most?) implementations by pure

Re: [fpc-pascal] glGetString crash

2018-02-19 Thread Jonas Maebe
Ryan Joseph wrote: >> On Feb 20, 2018, at 4:24 AM, Jonas Maebe wrote: >> >> My guess is that the Load_GL_VERSION_3_3x() function is broken since it >> appears to call glGetString before a context has been created, and that it >> just happens to work on some (most?) implementations by pure

[fpc-pascal] Cannot reference macro identifier in assembler code

2018-02-19 Thread Christo
The following code doesn't compile for the AVR target (FPC 38288): program macrotest; begin   asm   {$ifdef FPC_SRAMSIZE} sts FPC_SRAMSIZE , r31  // macrotest.pp(5,9) Error: Unknown identifier "FPC_SRAMSIZE"   {$endif}   end; end.  Is the use of macros in assembler blocks allowed?

Re: [fpc-pascal] glGetString crash

2018-02-19 Thread Jonas Maebe
On 19/02/18 03:21, Ryan Joseph wrote: Maybe SDL has a bug then because glGetString should never crash. glGetString is not an SDL function, but an OpenGL framework version. When are the land Load_GL_VERSION_XXX functions meant to be called in the pipeline? I was calling them before the