XC8 Compilers - Discussion

[mars01]

Patch may be working but with the new GCC "look', MPLABX can't see the xc.h therefore I reverted to XC8 1.45 which works fine.

[Catcatcat]

comparison of compilers v1.45 (pro) and 2.00 (s)


 




Posted on: June 23, 2018, 11:52:02 11:52 - Automerged

Patch may be working but with the new GCC "look', MPLABX can't see the xc.h therefore I reverted to XC8 1.45 which works fine.

In the beginning, there was a similar problem, re-install the compiler (before removing everything and the installation directory) and as described apply the medicine.


Posted on: June 23, 2018, 11:58:54 11:58 - Automerged
v2.00 C standart C 99

[mars01]

I guess we should stay away from v2.0 until they get the hang of it. The developers may have attempted too much for this release.

[metal]

what is the "new GCC "look'"? Did they abandon HI-TECH compilers?

[mars01]

what is the "new GCC "look'"? Did they abandon HI-TECH compilers?

I think they use a "wrapper". They still use the old compiler but it's deeper in the structure. They use Clang now and they support C99 and C90 as opposed to only C90(C89) up until v1.45.
It's because of the AVR compilers ...

[Manuel]

I confirm you your written.

So I think investigations should follow on 'xc8-cc.exe'..

take care,

Xo!

[metal]

I think they use a "wrapper". They still use the old compiler but it's deeper in the structure. They use Clang now and they support C99 and C90 as opposed to only C90(C89) up until v1.45.
It's because of the AVR compilers ...

I hope they don't kill microsoft IDE, it is better than Java crap..

[mars01]

I hope they don't kill microsoft IDE, it is better than Java crap..

I agree, actually I hope they start supporting PIC devices in Atmel Studio since they made the choice to use a GCC-like wrapper.

[alichan]

I guess we should stay away from v2.0 until they get the hang of it. The developers may have attempted too much for this release.

Amen... Adding C99 support is a major change and surely a major bug source.

[intel]

Hello there;
I could not get a pro mode of xc8 v2.0 version. I've done everything imaginable. After formatting the computer, I installed the xc8 v2.0 version directly. I don't know if anything was v1.45 installed before. I don't know if I'm connected to the internet. One of the masters should be interested.

[koky]

You must see the:
« Reply #172 on: June 13, 2018, 01:19:34 13:19 »
attention at the right BIN subdirectory

[intel]

You must see the:
« Reply #172 on: June 13, 2018, 01:19:34 13:19 »
attention at the right BIN subdirectory

Thanks koky;
I already made them. I think there is a changing license validation procedure.

[Top]

Open a command prompt as admin and run the following commands:

"C:\Program Files (x86)\Microchip\xc8\v2.00\bin\xclm.exe"
"C:\Program Files (x86)\Microchip\xc8\v2.00\pic\bin\xclm.exe"

Report back with results.

[intel]

Open a command prompt as admin and run the following commands:

"C:\Program Files (x86)\Microchip\xc8\v2.00\bin\xclm.exe"
"C:\Program Files (x86)\Microchip\xc8\v2.00\pic\bin\xclm.exe"

Report back with results.

"C:\Program Files\Microchip\xc8\v2.00\pic\bin\xclm.exe" did not pay attention to the new file location. Now the program as a result worked. Thank you so much Master Top.

[Catcatcat]

Compiler update released

MPLAB® XC8 Compiler v2.05

The microchip changed the principle of treatment, the "dancing with a tambourine" helped.   If you copy the missing files in the folder C: \ Program Files (x86) \ Microchip \ xc8 \ v2.05 \ pic \ bin, the compiler started working.

for comparison
v2.05 C standart C 99

[papy_bidouille]

7264 bytes less for my application I can add additional options
Thanks xclm.exe
And thank you to those who contributed.

[HackAndCrack]

What is the cracking procedure for XC8 v2.05 ?

I installed MPLAB X 5.10 and XC8 v2.05 yesterday and applied the crack as mentioned in latest sticky file and changed compiler options to Free, Standard and PRO and compiled but for all modes I get same .hex. I use PIC16F877A for a Blinky project.

[mars01]

What is the cracking procedure for XC8 v2.05 ?

I installed MPLAB X 5.10 and XC8 v2.05 yesterday and applied the crack as mentioned in latest sticky file and changed compiler options to Free, Standard and PRO and compiled but for all modes I get same .hex. I use PIC16F877A for a Blinky project.

Read the Reply #189, here: http://www.sonsivri.to/forum/index.php?topic=45707.msg191433#msg191433 it explain the extra steps.

It's quite simple.
1. Rename xclm file to xclm.old and copy the new xclm.exe file here:

Code:

C:\Program Files (x86)\Microchip\xc8\v2.05\bin

2. Copy both files (xclm.old and xclm.exe) from the previous location to:

Code:

C:\Program Files (x86)\Microchip\xc8\v2.05\pic\bin

and run the xclm.exe here as admin to patch the files.

There are no longer the options: Free, Standard and Pro. There are only different kinds of optimizations in GNU language like: O2, O3, O3 + s, some are available only for the licensed compiler.

[Manuel]

Did not investigated digging compiled but 2.05 is anyway bigger than 2.00 in both code and vars generation.

Then in 2.00 or previous the optimizer used to remove unused vars, the 2.05 leave them in.

Quite odd in this.

Those facts noted with Pic15F323 just for your interest...

Does anyone noticed this ?

X!

[Catcatcat]

Version 1.45 gives the most efficient optimization by code size.

[Manuel]

I will take time to investigate further so, since for the PIC12F510 there is no real difference between 2.00 and 2.05.

I will check 1.45 as well just for curiosity.

take care,
X!

[koky]

I have try with 2.09 and seem don't work

[Top]

I have try with 2.09 and seem don't work

Open a command prompt as admin and run the following commands:

"C:\Program Files (x86)\Microchip\xc8\v2.09\bin\xclm.exe"
"C:\Program Files (x86)\Microchip\xc8\v2.09\pic\bin\xclm.exe"

Report back with results.

[koky]

C:\Program Files (x86)\Microchip\xc8\v2.09\pic\bin>xclm.exe
Patched 40 bytes in file ./aspic.exe
Patched 40 bytes in file ./aspic18.exe
Patched 40 bytes in file ./cgpic.exe
Patched 40 bytes in file ./cgpic18.exe
Patched 40 bytes in file ./picc.exe
Patched 40 bytes in file ./picc18.exe
Patched SHA in 6 of 6 files

[Top]

So, does it work now?