[FFmpeg-devel] [PATCH] strict-aliasing-safe aes.c
Tue Jun 29 02:33:52 CEST 2010
On Mon, Jun 28, 2010 at 10:13:31PM +0200, Reimar D?ffinger wrote:
> On Mon, Jun 28, 2010 at 10:02:15PM +0200, Michael Niedermayer wrote:
> > On Mon, Jun 28, 2010 at 05:55:30PM +0200, Reimar D?ffinger wrote:
> > > Hello,
> > > this uses AV_WN32A, AV_WN64A etc. macros.
> > > The generated code is the same on x86_64 (assuming I did not mess up that test).
> > > aes.c | 20 +++++++++++++-------
> > > 1 file changed, 13 insertions(+), 7 deletions(-)
> > > 76705b63949d4abbe51b0d7d59537045ae91179a aesalias.diff
> > this makes the code unreadable, iam thus against it.
> Well, what is the alternative? The current code seems to not work with some compilers.
Fix the compiler.
Sorry if i appear as an asshole here but if one casts one pointer to another
and then dereferences it immedeatly afterwards then the compiler can be
expected to know what aliasses what. This is not the void pointer pushed
through a turring machine black box that the compiler cant figure out.
This language lawyering and pedantic gnu style compliance crussade is
really annoying. Anything that gnu considers to be worth warning about makes
people run and change their code, and often to the worse.
Where it doesnt affect readability and speed i dont mind if people change
the code to the latest gnu style, though i consider the whole a huge amount
of wasted time. In many cases its not the code but the compiler that needs
source code is supposed to be readable and maintainable, show me one
developer who considers the code after this patch more readable than before!
I guess you would also replace the c code by a base64 encoded string of a
gif file if part of the c spec required it.
what i think should be done is:
people should post a feature request on the <put affected compiler here> bug
tracker about it acting a bit more reasonable and handle such trivial
aliassing cases. And everyone who considers this important should reply
there and express his oppinon.
With a critical mass of compilers supporting this chances are probably good
to also get it into the C standard one day. And that would lead to more
readable and simpler code.
I dont mind us working around it here if theres some effort toward fixing
this where the problem is (aka compilers and the C spec) even if that effort
is small and unlikely to be successfull but if everything thats done is
directed toward turning every file into a unmaintaunable mess with not
one second spend on solving the actual problem then i dont think i
will approve such workarounds. Id like to have at least some hope even if
small that this red tape around every bit of optimized code one day would
> > Also its missing a benchmark
> The generated binary is identical, what is the point of benchmarking?
sorry, ive missed that they are identical
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Republics decline into democracies and democracies degenerate into
despotisms. -- Aristotle
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: Digital signature
More information about the ffmpeg-devel