Fix warning when building objects with a Q_OBJECT macro

Do not trigger a self-assign warning when running into code containing
a Q_OBJECT macro. Currently this happens a lot e.g. when using clang
to build code using Qt.

Change-Id: I68995624b18406f337318599e463f36f87486e66
(cherry-picked from qtbase commit 1416f4c595d6078c08f93483695e0b64c7fbb2a7)
Reviewed-by: Milian Wolff <milian.wolff@kdab.com>
Reviewed-by: Thiago Macieira <thiago.macieira@intel.com>
Use GET method for redirect in QDeclarativeXMLHttpRequest.

Initial-patch-by: Marek Więckowski <wiecko@fuw.edu.pl>

Task-number: QTBUG-32332
Change-Id: I393308134d60e484464e0cfc6cdcdac1edc27f8d
Reviewed-by: Peter Hartmann <phartmann@blackberry.com>
(cherry picked from qtquick1/e0f7b22341339b77aafa9150b0d79e320e9e4180)
Add support for the Linux/m68k platform

Add necessary support code to recognize m68k as an architecture;
use GCC builtin atomics like avr32 does. Copy avr32 header, since
it was hinted that including it from m68k was not liked.

This is not needed in Qt5 because it’s said to automatically use
the GCC atomic builtins.

Bug-Debian: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=660963

Task-number: QTBUG-28237
Change-Id: I6c51405c47549c904899a6971b6cd34b8239c642
Reviewed-by: Thiago Macieira <thiago.macieira@intel.com>