Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.c++ > #89389
| From | MarioCPPP <NoliMihiFrangereMentulam@libero.it> |
|---|---|
| Newsgroups | comp.lang.c++ |
| Subject | Re: strange error (QT Creator 4.12.2, based on QT creator 5.14.2) |
| Date | 2023-03-02 17:27 +0100 |
| Organization | A noiseless patient Spider |
| Message-ID | <ttqips$b9c8$2@dont-email.me> (permalink) |
| References | <ttqilb$b9c8$1@dont-email.me> |
On 02/03/23 17:25, MarioCPPP wrote: > > I have this situation : > > int32_t * Pointer32; // is a 4 byte signed int > int8_t * Pointer8; // is a "signed char" > // pointer allegedly "unaligned". > > Pointer32 = new int32_t [10]; > // supposedly ALIGNED a multiple of four byte addresses > > Pointer8 = static_cast <int8_t *> (Pointer32); Using an old style casts deserves just a warning ... Pointer8 = (int8_t *) (Pointer32); but it seems an ugly solution for a problem still not understood, so please explain me the "ratio" of the error with static_cast > > ERROR : STATIC CAST FROM int * to signed char * IS NOT ALLOWED. > > I am asking why that ? > > I mean, the reverse, maybe with a warning, seems weird (at > best very slow). > > But casting a MORE RESTRICTIVELY ALIGNED pointer to one LESS > RESTRICTIVELY ALIGNED seems pretty reasonable. Why not ? > > how comes I cannot access single bytes aligned whatever in > an int array ? > The type does not even have "NAN" problem or the drawback > i.g. of creating underflows, overflows, denormalized values > that can happen accessing FLOAT / DOUBLE on a random address > bytewise mode. > > But integral types SHOULD be accessible byte by byte without > problems, and a single byte does not have alignment > restrictions ... I am at a loss ! > help :D > -- 1) Resistere, resistere, resistere. 2) Se tutti pagano le tasse, le tasse le pagano tutti MarioCPPP
Back to comp.lang.c++ | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
strange error (QT Creator 4.12.2, based on QT creator 5.14.2) MarioCPPP <NoliMihiFrangereMentulam@libero.it> - 2023-03-02 17:25 +0100
Re: strange error (QT Creator 4.12.2, based on QT creator 5.14.2) MarioCPPP <NoliMihiFrangereMentulam@libero.it> - 2023-03-02 17:27 +0100
Re: strange error (QT Creator 4.12.2, based on QT creator 5.14.2) Bo Persson <bo@bo-persson.se> - 2023-03-02 17:44 +0100
Re: strange error (QT Creator 4.12.2, based on QT creator 5.14.2) Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-03-05 08:20 -0800
Re: strange error (QT Creator 4.12.2, based on QT creator 5.14.2) Andrey Tarasevich <andreytarasevich@hotmail.com> - 2023-03-02 09:44 -0800
Re: strange error (QT Creator 4.12.2, based on QT creator 5.14.2) MarioCPPP <NoliMihiFrangereMentulam@libero.it> - 2023-03-02 23:37 +0100
Re: strange error (QT Creator 4.12.2, based on QT creator 5.14.2) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-03-02 17:03 -0800
Re: strange error (QT Creator 4.12.2, based on QT creator 5.14.2) MarioCPPP <NoliMihiFrangereMentulam@libero.it> - 2023-03-03 13:22 +0100
Re: strange error (QT Creator 4.12.2, based on QT creator 5.14.2) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-03-03 09:29 -0800
Re: strange error (QT Creator 4.12.2, based on QT creator 5.14.2) MarioCPPP <NoliMihiFrangereMentulam@libero.it> - 2023-03-04 22:53 +0100
csiph-web