From: SourceForge.net <no...@so...> - 2006-05-28 14:29:56
|
Bugs item #1496419, was opened at 2006-05-28 14:29 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100599&aid=1496419&group_id=599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: rbras (rbras) Assigned to: Nobody/Anonymous (nobody) Summary: sdcc loops creating new symbol Initial Comment: 1. typedef struct _NODE { const unsigned char type; const unsigned char name[8]; const struct _NODE * const enter; const struct _NODE * const down; const struct _NODE * const up; }NODE; extern const NODE node1; extern const NODE node2; //sdcc loops allocating space for new symbols node1 and //zzz until there is no more memory, then segfaults // //The reference to zzz inside the declaration of zzz //triggers a loop allocating space for symbols node1 //and zzz const NODE zzz = {4, {'x', 'p', 't','o',0},&node1 , &zzz, &node2}; void Config() { } 2. I tried with differenet architectures and the result was the same. ex: sdcc -mpic16 -p18f452 -c lixo1.c 3. $ sdcc --version SDCC:mcs51/gbz80/z80/avr/ds390/pic16/pic14/TININative/xa51/ds400/hc08 2.5.6 #4195 (May 28 2006) (UNIX) 4. sdcc -mpic16 -p18f452 -c lixo1.c Segmentation fault see coments in the code for the explanatio of the segmentation fault. The code is valid. It works with microchip and hi-tech compilers. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100599&aid=1496419&group_id=599 |
From: SourceForge.net <no...@so...> - 2006-06-24 11:48:54
|
Bugs item #1496419, was opened at 2006-05-28 16:29 Message generated for change (Comment added) made by maartenbrock You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100599&aid=1496419&group_id=599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None >Group: fixed >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: rbras (rbras) >Assigned to: Maarten Brock (maartenbrock) Summary: sdcc loops creating new symbol Initial Comment: 1. typedef struct _NODE { const unsigned char type; const unsigned char name[8]; const struct _NODE * const enter; const struct _NODE * const down; const struct _NODE * const up; }NODE; extern const NODE node1; extern const NODE node2; //sdcc loops allocating space for new symbols node1 and //zzz until there is no more memory, then segfaults // //The reference to zzz inside the declaration of zzz //triggers a loop allocating space for symbols node1 //and zzz const NODE zzz = {4, {'x', 'p', 't','o',0},&node1 , &zzz, &node2}; void Config() { } 2. I tried with differenet architectures and the result was the same. ex: sdcc -mpic16 -p18f452 -c lixo1.c 3. $ sdcc --version SDCC:mcs51/gbz80/z80/avr/ds390/pic16/pic14/TININative/xa51/ds400/hc08 2.5.6 #4195 (May 28 2006) (UNIX) 4. sdcc -mpic16 -p18f452 -c lixo1.c Segmentation fault see coments in the code for the explanatio of the segmentation fault. The code is valid. It works with microchip and hi-tech compilers. ---------------------------------------------------------------------- >Comment By: Maarten Brock (maartenbrock) Date: 2006-06-24 13:48 Message: Logged In: YES user_id=888171 Fixed in SDCC 2.5.6 #4246. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100599&aid=1496419&group_id=599 |
From: SourceForge.net <no...@so...> - 2006-07-08 13:07:35
|
Bugs item #1496419, was opened at 2006-05-28 14:29 Message generated for change (Comment added) made by rbras You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100599&aid=1496419&group_id=599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: fixed Status: Closed >Resolution: Wont Fix Priority: 5 Submitted By: rbras (rbras) Assigned to: Maarten Brock (maartenbrock) Summary: sdcc loops creating new symbol Initial Comment: 1. typedef struct _NODE { const unsigned char type; const unsigned char name[8]; const struct _NODE * const enter; const struct _NODE * const down; const struct _NODE * const up; }NODE; extern const NODE node1; extern const NODE node2; //sdcc loops allocating space for new symbols node1 and //zzz until there is no more memory, then segfaults // //The reference to zzz inside the declaration of zzz //triggers a loop allocating space for symbols node1 //and zzz const NODE zzz = {4, {'x', 'p', 't','o',0},&node1 , &zzz, &node2}; void Config() { } 2. I tried with differenet architectures and the result was the same. ex: sdcc -mpic16 -p18f452 -c lixo1.c 3. $ sdcc --version SDCC:mcs51/gbz80/z80/avr/ds390/pic16/pic14/TININative/xa51/ds400/hc08 2.5.6 #4195 (May 28 2006) (UNIX) 4. sdcc -mpic16 -p18f452 -c lixo1.c Segmentation fault see coments in the code for the explanatio of the segmentation fault. The code is valid. It works with microchip and hi-tech compilers. ---------------------------------------------------------------------- >Comment By: rbras (rbras) Date: 2006-07-08 13:07 Message: Logged In: YES user_id=1530099 This bug is not fixed for the pic architecture. sdcc still gives a segmentation fault using sdcc -mpic16 -p18f452 ---------------------------------------------------------------------- Comment By: Maarten Brock (maartenbrock) Date: 2006-06-24 11:48 Message: Logged In: YES user_id=888171 Fixed in SDCC 2.5.6 #4246. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100599&aid=1496419&group_id=599 |
From: SourceForge.net <no...@so...> - 2006-07-08 13:09:32
|
Bugs item #1496419, was opened at 2006-05-28 14:29 Message generated for change (Settings changed) made by rbras You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100599&aid=1496419&group_id=599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None >Group: None >Status: Open Resolution: Wont Fix Priority: 5 Submitted By: rbras (rbras) Assigned to: Maarten Brock (maartenbrock) Summary: sdcc loops creating new symbol Initial Comment: 1. typedef struct _NODE { const unsigned char type; const unsigned char name[8]; const struct _NODE * const enter; const struct _NODE * const down; const struct _NODE * const up; }NODE; extern const NODE node1; extern const NODE node2; //sdcc loops allocating space for new symbols node1 and //zzz until there is no more memory, then segfaults // //The reference to zzz inside the declaration of zzz //triggers a loop allocating space for symbols node1 //and zzz const NODE zzz = {4, {'x', 'p', 't','o',0},&node1 , &zzz, &node2}; void Config() { } 2. I tried with differenet architectures and the result was the same. ex: sdcc -mpic16 -p18f452 -c lixo1.c 3. $ sdcc --version SDCC:mcs51/gbz80/z80/avr/ds390/pic16/pic14/TININative/xa51/ds400/hc08 2.5.6 #4195 (May 28 2006) (UNIX) 4. sdcc -mpic16 -p18f452 -c lixo1.c Segmentation fault see coments in the code for the explanatio of the segmentation fault. The code is valid. It works with microchip and hi-tech compilers. ---------------------------------------------------------------------- Comment By: rbras (rbras) Date: 2006-07-08 13:07 Message: Logged In: YES user_id=1530099 This bug is not fixed for the pic architecture. sdcc still gives a segmentation fault using sdcc -mpic16 -p18f452 ---------------------------------------------------------------------- Comment By: Maarten Brock (maartenbrock) Date: 2006-06-24 11:48 Message: Logged In: YES user_id=888171 Fixed in SDCC 2.5.6 #4246. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100599&aid=1496419&group_id=599 |
From: SourceForge.net <no...@so...> - 2006-07-08 20:21:10
|
Bugs item #1496419, was opened at 2006-05-28 16:29 Message generated for change (Comment added) made by maartenbrock You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100599&aid=1496419&group_id=599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. >Category: C-Front End >Group: fixed >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: rbras (rbras) Assigned to: Maarten Brock (maartenbrock) Summary: sdcc loops creating new symbol Initial Comment: 1. typedef struct _NODE { const unsigned char type; const unsigned char name[8]; const struct _NODE * const enter; const struct _NODE * const down; const struct _NODE * const up; }NODE; extern const NODE node1; extern const NODE node2; //sdcc loops allocating space for new symbols node1 and //zzz until there is no more memory, then segfaults // //The reference to zzz inside the declaration of zzz //triggers a loop allocating space for symbols node1 //and zzz const NODE zzz = {4, {'x', 'p', 't','o',0},&node1 , &zzz, &node2}; void Config() { } 2. I tried with differenet architectures and the result was the same. ex: sdcc -mpic16 -p18f452 -c lixo1.c 3. $ sdcc --version SDCC:mcs51/gbz80/z80/avr/ds390/pic16/pic14/TININative/xa51/ds400/hc08 2.5.6 #4195 (May 28 2006) (UNIX) 4. sdcc -mpic16 -p18f452 -c lixo1.c Segmentation fault see coments in the code for the explanatio of the segmentation fault. The code is valid. It works with microchip and hi-tech compilers. ---------------------------------------------------------------------- >Comment By: Maarten Brock (maartenbrock) Date: 2006-07-08 22:21 Message: Logged In: YES user_id=888171 Sorry, I forgot the PIC ports have their own glue.c. Fixed in SDCC 2.5.6 #4280. ---------------------------------------------------------------------- Comment By: rbras (rbras) Date: 2006-07-08 15:07 Message: Logged In: YES user_id=1530099 This bug is not fixed for the pic architecture. sdcc still gives a segmentation fault using sdcc -mpic16 -p18f452 ---------------------------------------------------------------------- Comment By: Maarten Brock (maartenbrock) Date: 2006-06-24 13:48 Message: Logged In: YES user_id=888171 Fixed in SDCC 2.5.6 #4246. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100599&aid=1496419&group_id=599 |