NO

Recent Posts

Pages: 1 [2] 3 4 ... 10
11
Beginner questions / Re: Linker Bug?
« Last post by John S. Kent on October 14, 2019, 05:20:01 am »
"Private #include files" That will take a few weeks to read & digest!!! Incredible amount of information! large number of functions, data types, macros, etc.  Extensive Extensions!

"Privata # inkludera filer" Det tar några veckor att läsa och smälta !!! Otrolig mängd information! stort antal funktioner, datatyper, makron osv. Omfattande tillägg

Google-översättning fungerar bra om man också kontrollerar den bakåtvända översättningen
12
Add-ins / Re: Syntax parser for .ispc
« Last post by Pelle on October 13, 2019, 10:50:44 pm »
Doesn't work well when insert a file to project, maybe a problem with 4 chars in ".ispc"
No known limitations on the length of a file extension, but it doesn't work well here either. Not sure why, I will have to investigate some day...

EDIT: Actually, right now a dependency scanner (AddFile.pfnScanner = Scanner) seems mandatory...
13
Beginner questions / Re: Linker Bug?
« Last post by Pelle on October 13, 2019, 10:47:30 pm »
   The Images of the "Win32 application wizard: Step 1 of 2" &
    "Win32 application wizard: Step 2 of 2"
   Has the Dialog button labels in a non-English language.
   Localization is difficult!, detailed, & complicated.
When this picture was made, it was impossible for my Swedish Windows version to display English (buttons). Considering only a handful of people will probably ever read this part of the documentation anyway, it seemed like a waste of time hand-editing the images (the text tells you what to do, and it's a standard Windows Property Sheet so it shouldn't be too surprising what to do, no?).

   Now moving on. where is the documentation that details the Pelles &
   Microsoft language extensions. List of functions? ... other features?
Well, the help page for the compiler project options ("Project" -> "Project options" -> "Compiler" and press "F1"), "IDE: Compiler project options dialog" says:
- for "Enable Microsoft extensions": see /Ze option (a hyperlink to be clicked).
- for "Enable Pelles C extensions": see /Zx option (a hyperlink to be clicked).
Those pages (for the /Ze option and /Zx option) will list the C language changes.

For C runtime functions, look under the "Content" tab in the help file. Everything under "Standard C #include files" is for standard C, everything under "Private #include files" is extensions of some kind (click enough "+"-signs to see extended functions, listed per #include file).


14
Expert questions / Re: linking ispc binaries.
« Last post by Pelle on October 13, 2019, 10:26:24 pm »
While waiting experts.
I'm waiting too...
15
Assembly discussions / Quicksort function from Pelles C run-time library
« Last post by Vortex on October 13, 2019, 11:40:34 am »
Here is a Quicksort example employing Pelles C run-time library :

Code: [Select]
include Sample.inc

CompareProc PROTO C :DWORD,:DWORD

NUMB_OF_ELEMENTS equ 10

.data

numbers     dd 29,12,32,65,58,7,12,11,11,97
format1     db '%d',13,10,0

.code

start:

    invoke  qsort,ADDR numbers,\
            NUMB_OF_ELEMENTS,\
            SIZEOF DWORD,ADDR CompareProc

    call    PrintArray

    invoke  ExitProcess,0
   
CompareProc PROC C arg1:DWORD,arg2:DWORD

    mov     ecx,arg1
    mov     edx,arg2
    mov     eax,DWORD PTR [ecx]
    sub     eax,DWORD PTR [edx]
    ret

CompareProc ENDP

PrintArray  PROC uses esi ebx

    mov     ebx,NUMB_OF_ELEMENTS
    mov     esi,OFFSET numbers
@@:
    invoke  printf,ADDR format1,\
            DWORD PTR [esi]

    add     esi,4
    dec     ebx
    jnz     @b
    ret

PrintArray ENDP

END start
16
Add-ins / Syntax parser for .ispc
« Last post by TimoVJL on October 10, 2019, 11:18:00 am »
Syntax parser for Intel SPMD Program Compiler
Doesn't work well when insert a file to project, maybe a problem with 4 chars in ".ispc"

EDIT: Scanner stub function added, as Pelle informed that it needs that.
17
Expert questions / Re: linking ispc binaries.
« Last post by danz68 on October 09, 2019, 12:50:55 pm »
These are great news.

I tried a similar test (custom code though), making a DLL and error was there.
(don't remember now error or code, I tried a couple of times then I gave up. It must be something else wrong).

Any new version since 9.00 Aug 2018?
18
Beginner questions / Linker Bug?
« Last post by John S. Kent on October 08, 2019, 06:53:13 pm »
Bug: ? & documentation not found

   I am completely new to the Pelles C tools.

   I started with the standard "Hello World" as a console application.

   Your first project: Hello, World. The Help Documentation has some
   language issues. See Help for "Integrated Environment"
   subsection: "POIDE integrated environment"

   The Images of the "Win32 application wizard: Step 1 of 2" &
    "Win32 application wizard: Step 2 of 2"
   Has the Dialog button labels in a non-English language.
   Localization is difficult!, detailed, & complicated.

   Getting past the documentation, the actual IDE Dialog components
   are all in the same language (English in my case).

   I got to the Project Menu & the Build "HelloConsoleApp.Exe".
   The source code file was "main.c" @ the time. I was able to compile
   main.c. However the linker failed. The problem turned out to be an
   issue with how the pathnames of the files are handled (& modified?).

   My original path was E:\John's\Pelles C Projects\HelloConsoleApp

   The Project output showed the above as:
   E:\John's\Pelles C Projects\HelloConsoleApp\main.c

   The linker failed; unable to find main.obj, it showed the path as

   E:\Johns\Pelles C Projects\HelloConsoleApp\output\main.obj

   See the problem?

   I changed the pathname to e:\Pelles C\HelloConsoleApp\

   Still miffed; Notice "John's" as opposed to "Johns". The IDE
   is improperly handling pathnames. I have fallen into these
   localization trap a few times.
   
   I now have 26 running applications.  Built with Pelles C IDE.
   I also use the Embarcadero C compiler (Borland) to build these
   same programs.

   Now moving on. where is the documentation that details the Pelles &
   Microsoft language extensions. List of functions? ... other features?

   I can not find that information anywhere in the documentation.
19
Expert questions / Re: linking ispc binaries.
« Last post by TimoVJL on October 08, 2019, 03:32:00 pm »
While waiting experts.

ispc generate normal object files, like PE-COFF.
tested simple example.
Code: [Select]
#include <stdio.h>
#include <stdlib.h>
// Include the header file that the ispc compiler generates
#include "simple_ispc.h"
//using namespace ispc;
#pragma comment(linker, "simple_ispc.o")

int main(void) {
    float vin[16], vout[16];

    // Initialize input buffer
    for (int i = 0; i < 16; ++i)
        vin[i] = (float)i;

    // Call simple() function from simple.ispc file
    simple(vin, vout, 16);

    // Print results
    for (int i = 0; i < 16; ++i)
        printf("%d: simple(%f) = %f\n", i, vin[i], vout[i]);

    return 0;
}
20
Expert questions / linking ispc binaries.
« Last post by danz68 on October 08, 2019, 02:57:33 pm »
Hi there,

Is it any possibility to link object files generated by ISPC
(https://ispc.github.io/ispc.html) with PellesC suite?

Same question for linking Microsoft libraries.

Thank you.

Pages: 1 [2] 3 4 ... 10